canary

Post-deploy monitoring detects reliability issues by watching a live web app and comparing it to a pre-deploy baseline. You can configure pages to monitor, capture screenshots, track console errors, and alert on performance anomalies after deployment.

Canary monitoring is a post-deploy check that continuously watches production health to catch regressions. You need it immediately after a deployment to verify page stability, detect console errors, and validate performance metrics against a baseline.

To capture console errors and performance metrics after a release, run a post-deploy monitoring loop against live URLs. The process takes periodic screenshots, records console errors, and compares performance metrics against a captured baseline to alert on anomalies.

Yes, a browse daemon is required to run post-deploy canary checks. It enables the live web app monitoring loop, allowing the system to browse configurable pages, capture screenshots, and validate production health against a baseline.

The best way to verify a deploy is to run a canary monitoring skill against the production URL. It automates a repeatable polling loop to watch the live app, compare screenshots and metrics to a baseline, and alert on detected anomalies.

Yes, post-deploy canary monitoring supports flexible page selection and duration control. You can configure which production pages to watch and set the monitoring duration to perform either a quick health check or an extended validation.