AWS RDS MySQL¶

Use the Guance Cloud Sync script package in the script market to synchronize cloud monitoring and cloud asset data to Guance

Configuration¶

Install Func¶

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

If deploying Func manually, refer to Manual Func Deployment

Install Script¶

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

Activate Script in Automata¶

1. Log in to the Guance 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 the cloud account information before, you can skip this step.
4. Click on 【Test】, and after the test is successful, click on 【Save】. If the test fails, please check if the relevant configuration information is correct and retest.
5. On the 【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, and under the Not Installed list, find AWS RDS MySQL, and click on the 【Install】 button. The installation interface will pop up for installation.

Manually Activate Script¶

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

2. Click on 【Install】, and 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 automatically configure the corresponding startup script.

4. After activation, you can see the corresponding automatic trigger configuration in 「Management / Automatic Trigger Configuration」. Click on 【Execute】 to immediately execute it once without waiting for the scheduled time. After a while, you can check the execution task record 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 record and logs to see if there are any exceptions.
2. In Guance, check if the asset information exists in 「Infrastructure / Custom」.
3. In Guance, check if there is corresponding monitoring data in 「Metrics」.

Metrics¶

After configuring Amazon CloudWatch, the default Measurement is as follows. You can collect more metrics through configuration Amazon CloudWatch Metrics Details

Amazon CloudWatch Instance-Level Metrics for Amazon RDS¶

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

Note:

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

Amazon CloudWatch Usage Metrics for Amazon RDS¶

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 a Quota Increase in the Service Quotas User Guide.

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

Object¶

The AWS RDS MySQL object data structure collected can be viewed in 「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"            : "{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 JSON serialized strings ```