AWS Aurora PostgreSQL

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

Configuration¶

Install Func¶

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

If deploying Func manually, refer to Manual Deployment of Func

Install Script¶

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

Activate Script in Automata¶

1. Log in to the TrueWatch console
2. Click on the 【Integration】 menu, select 【Cloud Account Management】
3. Click on 【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 on 【Test】, if the test is successful, click on 【Save】. If the test fails, please check if the relevant configuration information is correct and test again.
5. Click on 【Cloud Account Management】 list, you can see the added cloud account, click on the corresponding cloud account to enter the details page.
6. Click on the 【Integration】 button on the cloud account details page, find AWS Aurora PostgreSQL under the Not Installed list, click on the 【Install】 button, and install it in the pop-up installation interface.

Manually Activate Script¶

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

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

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

4. After activation, you can see the corresponding automatic trigger configuration in 「Manage / Automatic Trigger Configuration」. Click on 【Execute】 to execute it immediately without waiting for the scheduled time. After a while, you can check the execution task records and corresponding logs.

Verification¶

1. Confirm whether the corresponding task exists in 「Manage / Automatic Trigger Configuration」, and check the corresponding task records and logs for any exceptions.
2. In TrueWatch, check if asset information exists in 「Infrastructure - Resource Catalog」.
3. In TrueWatch, check if there are 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. In addition, 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 data structure of the collected AWS Aurora PostgreSQL objects can be viewed in 「Infrastructure - Resource Catalog」

{
  "measurement": "aws_rds",
  "tags": {
    "name"                     : "xxxxx",
    "RegionId"                 : "cn-northwest-1",
    "Engine"                   : "aurora-postgresql",
    "DBInstanceClass"          : "db.t3.medium",
    "DBInstanceIdentifier"     : "xxxxxx",
    "AvailabilityZone"         : "cn-northwest-1c",
    "SecondaryAvailabilityZone": "ap-southeast-1c"
  },
  "fields": {
    "InstanceCreateTime"  : "2025-05-19T19:54:07.871Z",
    "LatestRestorableTime": "2025-05-19T19:54:07.871Z",
    "Endpoint"            : "{Connection Address JSON Data}",
    "AllocatedStorage"    : 100,
    "message"             : "{Instance JSON Data}",
  }
}

Note: The fields in tags and 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 all JSON serialized strings.