canary

Post-deploy monitoring checks a live URL every 60 seconds to detect console errors, performance regressions, and visual changes, comparing the deployed state against a captured baseline to alert you to anomalies for fast reliability verification.

A baseline capture records the healthy state of your pages before a deployment. You need it during production monitoring to establish a reference point for detecting visual changes, console errors, and performance regressions after new code goes live.

Configure target pages, monitoring duration, and alert rules to start a canary run. The system automatically loads live pages every 60 seconds, checks for anomalies against the baseline, and generates a structured health report for post-deploy verification.

Yes, you need a browse daemon to load live pages for post-deploy canary monitoring. The daemon enables the system to render URLs, capture the baseline, and perform the automated per-page checks required to detect visual and performance regressions.

Yes, production monitoring supports configurable pages, duration, and alert rules. You can define which specific URLs to watch, set the monitoring window, and establish custom alerting thresholds to receive a structured canary report for post-deploy verification.

A structured canary report includes the results of automated per-page checks for console errors, performance regressions, and visual changes. It surfaces actionable alerts based on your configured rules and the captured baseline to verify post-deploy reliability.