Posted On: Mar 15, 2024

Amazon CloudWatch Synthetics, an outside-in monitoring capability to continually verify your customers’ experience using snippets of code called canaries, is extending historical data for canary runs that pass or fail from 7-days to 30-days. Canary run troubleshooting artifacts such as screenshots from the canary run, HAR files, and log files for historical runs can be viewed for up to 30 days to easily pin point persistent versus intermittent canary run failure patterns on the CloudWatch console.

Canary runs from CloudWatch Synthetics are also integrated with the new application performance monitoring (APM) capability CloudWatch Application Signals (in Preview). As a result, historical canary pass or fail trends can easily be correlated with performance metrics such as errors, faults, and latency observed in your APIs (service operations) and dependencies to root cause operational health issue of your application.

Historical canary run data is available at no additional cost in all commercial AWS Regions and the China regions (Beijing and Ningxia). Canary run artifacts continue to be stored in the Amazon S3 bucket specified by you and charged at standard Amazon S3 rates. You can optionally configure Amazon S3 lifecycle policies to expire canary artifacts, say after 30 days.

To get started with viewing historical data, View Canary Statistics and Details. To Learn more about application performance monitoring, visit Amazon CloudWatch Application Signals