canary

To monitor production for performance regressions after deployment, run a post-deploy canary check using a browse daemon to continuously watch live app pages, capture baselines, and emit alerts for anomalies.

A post-deploy canary check is an automated monitoring process that detects page failures by continuously watching a live app for console errors and performance regressions, comparing against captured baselines while taking screenshots of anomalies.

Capture baselines and generate health reports by initiating a canary monitoring session which captures baseline page behavior, then continuously checks pages and outputs a canary report for review after the configured duration.

Yes, you can select specific pages for post-deploy verification and configure the monitoring duration, with a default runtime of 10 minutes, allowing targeted per-page monitoring and quick health checks via browser-driven checks.

A browse daemon is required for continuous production monitoring because it drives the browser-driven checks necessary to detect console errors, performance regressions, and page failures while taking baseline-aware screenshots.

Yes, post-deploy canary monitoring supports alerting for console errors by continuously watching the live app, comparing runtime behavior against captured baselines, and emitting alerts when anomalies are detected.