canary

To monitor a production URL for errors post-deploy, you can use a canary monitor with a browser daemon to watch live pages for console errors, performance regressions, and page failures. It compares against pre-deploy baselines and alerts on detected anomalies.

Post-deploy canary monitoring is an early issue detection technique that watches live pages using a browser daemon. It detects performance regressions by measuring page load health and comparing current metrics against saved pre-deployment baselines to identify anomalies.

Run the canary command with the target URL to start a 10-minute monitoring session. You can use optional flags to customize the duration, specify multiple pages to validate, and capture a pre-deploy baseline for comparison.

Yes, post-deploy canary monitoring validates critical user flows across multiple routes. The browser daemon records console errors, takes periodic screenshots, measures performance, and verifies page load health across the configured paths.

Pre-deploy baselines are used for comparing post-deploy performance and detecting anomalies. The canary monitor saves baselines and alerts on regressions, but you can also spot-check critical paths and validate page load health independently during a configured monitoring duration.

Canary monitoring is designed for post-deploy reliability checks and spot-checking critical paths. It should not be used as a replacement for pre-deploy testing, but rather as an early warning system for console errors, page failures, and performance regressions in live production environments.