canary

Post-deploy canary monitoring uses a browse daemon to check production web apps for console errors, performance regressions, and page failures after a new release. It takes periodic screenshots and raises alerts when anomalies are detected.

Baseline-aware canary monitoring captures pre-deploy page screenshots and compares them against live production pages. This mechanism catches visual and performance regressions before customers notice by detecting anomalies during periodic monitoring windows.

Configure your production URL and pre-deploy baseline, then run the canary against the URL. The browse daemon takes periodic screenshots during the monitoring window to verify critical pages load correctly without console errors.

Yes, post-deploy canary monitoring supports page-target options for web apps. You can configure specific production URLs to monitor, allowing the browse daemon to capture screenshots and compare them against baselines for targeted health checks.

Yes, a browse daemon is required to take screenshots, compare against baselines, and detect page failures or console errors. It enables real-time post-deploy health checks by monitoring production URLs during periodic windows.

Canary monitoring applies specifically to post-deploy checks on web apps. It requires a pre-deploy baseline for effective regression detection and relies on a browse daemon to capture screenshots and generate alerts for production anomalies.