canary

Post-deploy monitoring catches production issues early by continuously watching for console errors, performance regressions, and page failures. It uses a browse daemon to observe live deployments and captures baseline screenshots for comparison.

Baseline screenshot comparison captures page states before deployment, then continuously checks live pages against these baselines to detect anomalies. This process identifies visual regressions and page failures by comparing current production states to the recorded baseline evidence.

Setting up continuous page health checks with a browse daemon involves providing a URL to start automatic post-deploy monitoring. The daemon auto-discovers or uses specified pages, captures screenshots and logs, and runs health checks for a default duration of 10 minutes.

Yes, you need the browse tool to run post-deploy canary monitoring. The canary process relies on the browse daemon to observe live deployments, capture baseline screenshots, auto-discover pages, and continuously check production health for anomalies.

The best way to catch production issues before users notice them is post-deploy canary monitoring. By capturing baseline screenshots and continuously watching for console errors and performance regressions, you receive early alerts with evidence to address problems proactively.

When production health checks fail, a canary report provides evidence of anomalies, alerts for console errors and performance regressions, and page failure logs. It also includes an option to update the baseline once the application returns to a healthy state.