Skip to content

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 ReadOnlyAccess directly.

Activate the script in Hosted Func

  1. Log in to the Guance 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 the cloud account information before, ignore this step
  4. 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
  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 [Integrations] on the cloud account details page. Find AWS Route53 Resolver in the Not installed list and click [Install] to open the installation dialog. Select the region of the Resolver Endpoint and install.

Activate the script manually

  1. Sign in to the Func console, click [Script Market], open the Guance script market, and search for integration_aws_cloudwatch.
  2. Click 【Install】 and enter AWS AK ID, AK Secret, and the account name.
  3. Click [Deploy Startup Script]. The system automatically creates the Startup script set and configures the corresponding startup script. Set regions to the region of the Resolver Endpoint, replace the entire collector_configs['targets'] with [{'namespace': 'AWS/Route53Resolver', 'metrics': ['EndpointHealthyENICount', 'EndpointUnhealthyENICount']}], and remove the InstanceId dimension from the original EC2 target.
  4. 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

  1. Under 「Management / Automatic Trigger Configuration」, confirm that the task is configured and review its records and logs for permission or API errors.
  2. In Guance, open [Metrics] and check the aws_route_53_resolver measurement 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

Feedback

Is this page helpful?