AWS Route 53 provides DNS and traffic management along with availability and performance monitoring through health checks. You can view the health check information in Datadog to provide context around other metrics and events in your environments. Here’s an example dashboard of Route 53’s health check status graph:
For information about the rest of the AWS services, see the AWS tile
If you haven’t already, set up the Amazon Web Services integration first.
In the AWS integration tile, ensure that Route53 is checked under metric collection.
Add those permissions to your Datadog IAM policy in order to collect Amazon Route53 metrics:
route53:listHealthChecks: List available health checks.route53:listTagsForResources: Add custom tags on Route53 CloudWatch metrics.For more information, see the Route53 policies on the AWS website.
Install the Datadog - AWS Route53 integration.
Note: To get Amazon Route 53 metrics using CloudWatch, you must choose US East (N. Virginia) as the region. Amazon Route 53 metrics are not available if you select any other region. See Monitoring health check status and getting notifications for more information.
Configure Amazon Route 53 to log information about the queries that Route 53 receives, such as the following:
Go to your Route 53 AWS console and select the hosted zone you want to configure log for. Click on the radio button and select “configure query logging”.
Then select the CloudWatch log group or create a new one you want to send the logs to. Make sure “route53” is included in the log group name.
Select Query Logging under Resolver in Route 53 settings pane.
Click on Configure Query Logging and follow the steps to define the VPCs that you want to log resolver queries for, select the CloudWatch log group you want to send them to, and optionally define tags. Make sure “route53” is included in the log group name.
Once done, go in your Datadog Log section to start exploring your logs!
|
aws.route53.health_check_percentage_healthy (gauge) |
The percentage of Amazon Route 53 health checkers that consider the selected endpoint to be healthy. Shown as percent |
|
aws.route53.health_check_status (gauge) |
The status of the health check endpoint that CloudWatch is checking. 1 indicates healthy, and 0 indicates unhealthy. |
|
aws.route53.connection_time (gauge) |
The average time that it took Amazon Route 53 health checkers to establish a TCP connection with the endpoint. Shown as millisecond |
|
aws.route53.time_to_first_byte (gauge) |
The average time that it took Amazon Route 53 health checkers to receive the first byte of the response to an HTTP or HTTPS request. Shown as millisecond |
|
aws.route53.sslhandshake_time (gauge) |
The average time that it took Amazon Route 53 health checkers to complete the SSL handshake. |
|
aws.route53.child_health_check_healthy_count (gauge) |
For a calculated health check, the number of health checks that are healthy among the health checks that Amazon Route 53 is monitoring. |
|
aws.route53.dnsqueries (count) |
The number of DNS queries that Route53 responds to for all records in a hosted zone. Shown as query |
|
aws.route53resolver.inbound_query_volume (count) |
The number of DNS queries forwarded from your network to your VPCs through the endpoint specified by EndpointId. Shown as query |
|
aws.route53resolver.outbound_query_volume (count) |
The number of DNS queries forwarded from your VPCs to your network through the endpoint specified by EndpointId. Shown as query |
|
aws.route53resolver.outbound_query_aggregate_volume (count) |
The number of DNS queries forwarded from your VPCs to your network through the endpoint that is specified by EndpointId. Shown as query |
Each of the metrics retrieved from AWS are assigned the same tags that appear in the AWS console, including but not limited to host name, security-groups, and more.
The AWS Route 53 integration does not include any events.
The AWS Route 53 integration does not include any service checks.
Need help? Contact Datadog support.
