AWS RDS MySQL¶

Use the script packages in the script market named 「Guance Cloud Sync」 series to synchronize cloud monitoring and cloud asset data to Guance

Configuration¶

Install Func¶

It is recommended to activate Guance integration - extension - hosted Func: all prerequisites are automatically installed. Please proceed with script installation.

If you deploy Func on your own, refer to Self-deployed Func

Script Installation¶

Note: Please prepare an Amazon AK that meets the requirements in advance (for simplicity, you can directly grant global read-only permission ReadOnlyAccess).

Hosted Edition Script Activation¶

1. Log in to the Guance console.
2. Click on the 【Manage】 menu and select 【Cloud Account Management】.
3. Click 【Add Cloud Account】, choose 【AWS】, and fill in the required information on the interface. If you have already configured cloud account information before, skip this step.
4. Click 【Test】. After a successful test, click 【Save】. If the test fails, check whether the related configuration information is correct and retest.
5. In the 【Cloud Account Management】 list, you can see the added cloud accounts. Click the corresponding cloud account to enter the details page.
6. Click the 【Integration】 button on the cloud account details page. Under the Not Installed list, find AWS RDS MySQL, click the 【Install】 button, and follow the prompts to complete the installation.

Manual Script Activation¶

1. Log in to the Func console, click 【Script Market】, go to the official script market, and search for: guance_aws_rds.

2. After clicking 【Install】, input the corresponding parameters: AWS AK ID, AK Secret, and account name.

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

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

Verification¶

1. Confirm under 「Management / Automatic Trigger Configuration」 whether the corresponding tasks have the corresponding automatic trigger configurations, and check the corresponding task records and logs for any anomalies.
2. In Guance, under 「Infrastructure / Custom」, check if there is asset information.
3. In Guance, under 「Metrics」, check if there is corresponding monitoring data.

Metrics¶

After configuring Amazon - CloudWatch, the default measurement sets are as follows. More metrics can be collected through configuration. Refer to Amazon CloudWatch Metrics Details

Amazon RDS Instance-level Metrics in Amazon CloudWatch¶

The AWS/RDS namespace in Amazon CloudWatch includes the following instance-level metrics.

Note:

The Amazon RDS console may display metrics in units different from those sent to Amazon CloudWatch. For example, the Amazon RDS console might display a metric in megabytes (MB), while sending it to Amazon CloudWatch in bytes.

Amazon RDS Usage Metrics in Amazon CloudWatch¶

The AWS/Usage namespace in Amazon CloudWatch includes account-level usage metrics for Amazon RDS service quotas. CloudWatch automatically collects usage metrics for all AWS regions.

For more information, see CloudWatch Usage Metrics in the Amazon CloudWatch User Guide. For more information about quotas, see Quotas and Limits for Amazon RDS and Requesting an Increase in Quota in the Service Quotas User Guide.

* Amazon RDS does not publish the units of usage metrics to CloudWatch. These units appear only in the documentation.

Objects¶

Collected AWS RDS MySQL object data structure can be viewed under 「Infrastructure - Custom」

{
  "measurement": "aws_rds",
  "tags": {
    "name"                     : "xxxxx",
    "RegionId"                 : "cn-northwest-1",
    "Engine"                   : "mysql",
    "DBInstanceClass"          : "db.t3.medium",
    "DBInstanceIdentifier"     : "xxxxxx",
    "AvailabilityZone"         : "cn-northwest-1c",
    "SecondaryAvailabilityZone": "cn-northwest-1d"
  },
  "fields": {
    "InstanceCreateTime"  : "2018-03-28T19:54:07.871Z",
    "LatestRestorableTime": "2018-03-28T19:54:07.871Z",
    "Endpoint"            : "{JSON Data for Connection Address}",
    "AllocatedStorage"    : 100,
    "message"             : "{JSON Serialized Instance Data}",
  }
}

Note: Fields in tags and fields may change with subsequent updates.

Tip 1: The value of tags.name is the instance ID, which serves as unique identification.

Tip 2: fields.message and fields.Endpoint are JSON serialized strings.