AWS Route53 Resolver
Collect network interface health metrics for AWS Route53 Resolver endpoints.
Configuration¶
Install Func¶
We recommend enabling Hosted Func under Guance Integrations - Extensions. All prerequisites are installed automatically; continue with script installation.
For a self-hosted Func deployment, see Self-host Func.
Activate Script¶
Note: Prepare an AWS AK that meets the requirements. For simplicity, you can grant the global read-only permission
ReadOnlyAccessdirectly.
Activate the script in Hosted Func¶
- Log in to the Guance console
- Click the 【Integration】 menu and select 【Cloud Account Management】
- Click 【Add Cloud Account】, select 【AWS】, and fill in the required information on the interface. If you have already configured the cloud account information before, ignore this step
- Click 【Test】, and if the test is successful, click 【Save】. If the test fails, please check if the relevant configuration information is correct and test again
- 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
- Click [Integrations] on the cloud account details page. Find
AWS Route53 Resolverin theNot installedlist and click [Install] to open the installation dialog. Select the region of the Resolver Endpoint and install.
Activate the script manually¶
- Sign in to the Func console, click [Script Market], open the Guance script market, and search for
integration_aws_cloudwatch. - Click 【Install】 and enter AWS AK ID, AK Secret, and the account name.
- Click [Deploy Startup Script]. The system automatically creates the
Startupscript set and configures the corresponding startup script. Setregionsto the region of the Resolver Endpoint, replace the entirecollector_configs['targets']with[{'namespace': 'AWS/Route53Resolver', 'metrics': ['EndpointHealthyENICount', 'EndpointUnhealthyENICount']}], and remove theInstanceIddimension from the original EC2 target. - after enabling it, open"Management / Automatic Trigger Configuration"to view the automatic trigger configuration.Click[Run],to run it immediately,without waiting for the scheduled interval.wait a moment,you can view execution records and related logs
Verification¶
- Under 「Management / Automatic Trigger Configuration」, confirm that the task is configured and review its records and logs for permission or API errors.
- In Guance, open [Metrics] and check the
aws_route_53_resolvermeasurement for the monitoring data.
Metrics¶
After configuring AWS cloud monitoring, the default metrics are listed below. You can configure additional metrics for collection.AWS Route53 Resolver Metric details
AWS Route53 Resolver metrics are in the aws_route_53_resolver measurement.
| MetricName | MetricDescribe | Dimensions | Unit |
|---|---|---|---|
endpoint_healthy_enicount_average |
Healthy elastic network interfaces in the endpoint in OPERATIONAL state | endpoint_id, region_id | count |
endpoint_unhealthy_enicount_average |
Unhealthy elastic network interfaces in the endpoint in AUTO_RECOVERING state | endpoint_id, region_id | count |