canary

You can monitor a production URL post-deployment by taking periodic screenshots, checking console errors, and comparing current behavior against a baseline. This captures regressions early using the browse daemon to assess application health.

Post-deploy canary monitoring watches a live application after a release to catch silent degradations caused by environment differences or misconfigurations. You need it to detect performance regressions or page failures before users are widely affected.

Yes, the browse daemon is required to run post-deploy canary monitoring. It enables the skill to access configured production pages, take periodic screenshots, capture baseline behavior, and log anomaly alerts.

You can configure monitoring by using the --duration, --baseline, and --pages options. This specifies how long to watch, sets baseline captures, and targets specific production pages for anomaly detection and reporting.

Deployments can silently degrade due to environment differences, misconfigurations, or slow network paths. Canary monitoring catches these issues by periodically capturing screenshots and comparing current behavior against a baseline to alert on anomalies.