canary

Post-deploy monitoring automates watching a live URL for console errors, performance regressions, and broken pages. By capturing a baseline and performing periodic checks, it emits alerts when production anomalies are detected.

Canary monitoring is a post-deploy validation process that watches live pages to catch issues before users notice them. You need it when changes slip past CI and expose reliability gaps in production environments.

You can run an automated health check by targeting the live URL with a canary command. The skill uses the browse daemon to take baselines, perform periodic checks over a set duration, and output a health report.

Yes, the browse daemon is required to perform continuous post-deploy monitoring. It enables the skill to watch live pages, capture baselines, and emit alerts when performance regressions or page failures are detected.

The best way to catch performance regressions is running automated post-deploy monitoring that takes baselines and performs periodic checks. This canary approach validates critical paths remain healthy and emits alerts for remediation.

Post-deploy monitoring runs for a configurable duration to validate production health. A typical canary run monitors the site for 10 minutes, checking critical paths against baselines and emitting alerts if anomalies are detected.