Amazon Route 53

Crawler

Overview

AWS Route 53 provides DNS and traffic management along with availability and performance monitoring via 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

Setup

Installation

If you haven’t already, set up the Amazon Web Services integration first.

Metric collection

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 on Route53 policies, review the documentation 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.” Read more here

Log collection

Configure Amazon Route 53 to log information about the queries that Route 53 receives, such as the following:

The domain or subdomain that was requested
The date and time of the request
The DNS record type (such as A or AAAA)
The Route 53 edge location that responded to the DNS query
The DNS response code, such as NoError or ServFail

Enable Route53 Logging

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.

Send logs to Datadog

If you haven’t already, set up the Datadog log collection AWS Lambda function.
Once the lambda function is installed, manually add a trigger on the Cloudwatch Log group that contains your Route53 logs in the AWS console:

Select the corresponding CloudWatch Log group, add a filter name (but feel free to leave the filter empty) and add the trigger:

Once done, go in your Datadog Log section to start exploring your logs!

Data Collected

Metrics

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.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 count
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 count

Each of the metrics retrieved from AWS will be assigned the same tags that appear in the AWS console, including but not limited to host name, security-groups, and more.

Events

The AWS Route 53 integration does not include any events.

Service Checks

The AWS Route 53 integration does not include any service checks.

Troubleshooting

Need help? Contact Datadog support.