Once you’ve integrated with AWS CloudWatch, you have access to metrics from AWS Route 53, which manages the three primary tasks of domain registration, DNS routing, and health checking in any combination.
To verify metrics are reporting, search for the metrics on the Metric details page in Settings.
The following table shows the Route 53 metrics ingested by Cloud Observability.
|The percentage of calculated health checks that are sound out of all the ones that Route 53 is keeping track of.
|The typical time in milliseconds used by Route 53 health checkers to connect to the endpoint over TCP. You can view ConnectionTime for a health check for either the entire world or just a particular location.
|The proportion of Route 53 health checkers who believe the chosen terminus to be in good health. Data for a particular region is not accessible; you can only view HealthCheckPercentageHealthy when it applies to all regions. This is configured in the Latency graphs option. Reading Monitoring the latency between health checkers and your endpoint for more information is advised.
|The current state of the endpoint's health check that CloudWatch is examining. A value of 1 denotes good health, whereas a value of 0 denotes bad health. HealthCheckStatus information is only accessible for viewing across all regions; data for a particular region is not available. This is configured in the Latency graphs option. Reading Monitoring the latency between health checkers and your endpoint for more information is advised.
|The typical SSL handshake time, in milliseconds, that Route 53 health checkers took. In order to perform a health check, you may either inspect the SSLHandshakeTime for all regions or just the one you've chosen.
|The typical wait time in milliseconds seen by Route 53 health checkers before getting the first byte of a response to an HTTP or HTTPS request. Depending on your preference, you can see TimeToFirstByte for a health check for all areas or just a particular one.
Updated Dec 1, 2022