gstack-canary

Post-deploy monitoring watches a live app for console errors, performance regressions, and page failures using the browse daemon. It captures periodic screenshots and compares them against pre-deploy baselines to alert you on anomalies within a defined duration.

A canary check is a deterministic monitoring process that validates live application behavior immediately after a deployment. You need it to detect performance regressions and page failures by comparing live telemetry and screenshots against pre-deploy baselines.

You can configure optional telemetry, baselines, and page coverage to support deterministic canary runs. Start monitoring by running the canary command against your target URL with optional flags to customize duration, pages, and baseline comparison behavior.

Yes, the browse daemon supports baseline capture by taking periodic screenshots of your live application. These pre-deploy baselines are then compared against live post-deploy telemetry and visual states to alert you when anomalies appear.

The best way to detect post-release regressions is running automated canary checks that monitor live page behavior against pre-deploy baselines. This approach captures screenshots and console errors, alerting you to page failures and performance issues within a defined duration.

Post-deploy screenshot monitoring requires pre-deploy baselines for comparison and is limited to detecting visual and console anomalies within a configured duration. It relies on the browse daemon to watch specific pages, meaning unmonitored routes will not be checked for failures.