canary

Post-deploy monitoring captures baseline snapshots of production URLs and continuously checks for console errors, performance regressions, and page failures to catch production issues before users notice. It uses the browse daemon for automated anomaly detection.

Canary monitoring is the phase-driven process of capturing pre-deploy baseline snapshots of production pages, then continuously checking post-deploy URLs against that baseline to detect visual, console, or performance anomalies. You need it for automated post-deploy verification workflows.

Yes, the browse daemon is required to perform continuous health checks across multiple pages. It enables the browse-based monitoring needed to capture baselines, discover pages, and surface actionable findings when anomalies are detected after a deploy.

Yes, page discovery and periodic health checks can be manually triggered to support post-deploy verification workflows. You can invoke the monitoring process with a URL to start baseline capture, select specific pages, and begin continuous checks after deploy.

Automated alerting is configured by capturing a baseline, selecting pages to monitor, and running continuous health checks that compare post-deploy states against the baseline. When anomalies like page failures or performance regressions are detected, the system surfaces actionable findings.

Baseline comparison captures a pre-deploy snapshot of page performance and console state, then continuously monitors the same pages post-deploy. When post-deploy checks deviate from the captured baseline, the system flags the anomalies as actionable findings.