AWS Aurora MySQL

Use the TrueWatch Cloud Sync script packages in the script market to sync cloud monitoring and cloud asset data to TrueWatch

Configuration¶

Install Func¶

It is recommended to enable the TrueWatch Integration - Extension - DataFlux Func (Automata): All prerequisites are automatically installed, please proceed with the script installation.

If you are deploying Func yourself, refer to Self-deploying Func

Install Script¶

Note: Please prepare the required Amazon AK in advance (for simplicity, you can directly grant global read-only permissions ReadOnlyAccess)

Enable Script for Automata¶

1. Log in to the TrueWatch console
2. Click the 【Integration】 menu and select 【Cloud Account Management】
3. Click 【Add Cloud Account】, select 【AWS】, and fill in the required information on the interface. If you have already configured cloud account information before, ignore this step
4. Click 【Test】, and after successful testing, click 【Save】. If the test fails, please check if the relevant configuration information is correct and test again
5. Click 【Cloud Account Management】, and you can see the added cloud account in the list. Click the corresponding cloud account to enter the details page
6. Click the 【Integration】 button on the cloud account details page, find AWS Aurora MySQL under the Not Installed list, click the 【Install】 button, and the installation interface will pop up for installation.

Manually Enable Script¶

1. Log in to the Func console, click 【Script Market】, enter the TrueWatch script market, and search: integration_aws_aurora_mysql

2. Click 【Install】, and enter the corresponding parameters: AWS AK ID, AK Secret, and account name.

3. Click 【Deploy Startup Script】, the system will automatically create the Startup script set and automatically configure the corresponding startup script.

4. After enabling, you can see the corresponding automatic trigger configuration in 「Management / Automatic Trigger Configuration」. Click 【Execute】 to execute immediately without waiting for the scheduled time. Wait a moment, and you can view the execution task records and corresponding logs.

Verification¶

1. In 「Management / Automatic Trigger Configuration」, confirm whether the corresponding task has the corresponding automatic trigger configuration, and you can also check the corresponding task records and logs to check for any abnormalities
2. In TrueWatch, check if asset information exists in 「Infrastructure - Resource Catalog」
3. In TrueWatch, check if there is corresponding monitoring data in 「Metrics」

Metrics¶

Configure Amazon CloudWatch to collect more metrics Amazon CloudWatch Metrics Details

Amazon CloudWatch Metrics for Amazon RDS¶

The AWS/RDS namespace includes the following metrics, which apply to database entities running on Amazon Aurora. Some metrics apply to Aurora MySQL and/or Aurora PostgreSQL. Additionally, some metrics are specific to database clusters, primary database instances, replica database instances, or all database instances.

Cluster-level Metrics for Amazon Aurora¶

Instance-level Metrics for Amazon Aurora¶

Unless otherwise noted, the following instance-specific Amazon CloudWatch metrics apply to all Aurora MySQL and Aurora PostgreSQL instances.

Objects¶

The collected AWS Aurora MySQL object data structure can be seen in 「Infrastructure - Resource Catalog」

{
  "measurement": "aws_rds",
  "tags": {
    "name"                     : "xxxxx",
    "RegionId"                 : "cn-northwest-1",
    "Engine"                   : "aurora-mysql",
    "DBInstanceClass"          : "db.t3.medium",
    "DBInstanceIdentifier"     : "xxxxxx",
    "AvailabilityZone"         : "ap-southeast-1b",
    "SecondaryAvailabilityZone": "ap-southeast-1c"
  },
  "fields": {
    "InstanceCreateTime"  : "2025/05/26 22:45:02",
    "LatestRestorableTime": "2025/05/26 22:15:26",
    "Endpoint"            : "{Connection Address JSON Data}",
    "AllocatedStorage"    : 1,
    "message"             : "{Instance JSON Data}",
  }
}

Note: The fields in tags, fields may change with subsequent updates

Tip 1: The value of tags.name is the instance ID, used as a unique identifier

Tip 2: fields.message, fields.Endpoint are JSON serialized strings ```