canary

Post-deploy production monitoring tracks a live URL to detect console errors, performance regressions, and page failures. It takes screenshots, collects logs, and compares metrics against baselines to alert on anomalies before users notice.

Baseline capture records initial page health metrics and visual states before changes occur. You need baseline capture during post-deploy validation to compare current performance and console logs against known-good states to identify regressions.

To run a canary monitoring session, execute the monitor command with your target production URL after deploying. This initiates a ten-minute session where the browse daemon takes screenshots, collects logs, and checks for anomalies.

Yes, post-deploy monitoring works across multiple pages or a defined page set. You can apply page-level checks to a targeted list of URLs to capture visual and performance metrics across your production environment.

Yes, post-deploy monitoring uses a browse daemon to take screenshots, collect console logs, and compare page performance against baselines. The daemon provides the live health signals needed to detect page failures and anomalies.

Post-deploy monitoring alerts on anomalies to catch subtle performance regressions and console errors that do not cause outright page failures. Comparing against baselines helps detect these issues early to guide debugging before users notice.