canary

Monitor deployed web apps for console errors and performance regressions.

4|1|Updated Sep 13, 2023
One-click install
npx skills add https://github.com/louisfghbvc/mcp-leetcode-crawler --skill canary-louisfghbvc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canary
Source: https://github.com/louisfghbvc/mcp-leetcode-crawler/tree/main/.agent/skills/canary
Command: npx skills add https://github.com/louisfghbvc/mcp-leetcode-crawler --skill canary-louisfghbvc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-deploy canary monitoring helps catch production issues before users notice, by watching the live app for console errors, performance regressions, and page failures using the browse daemon.

Core Features & Use Cases

  • Monitor post-deploy health across selected pages and durations.
  • Take periodic screenshots, baseline comparisons, and alert on anomalies.
  • Automatically generate baseline captures and compare against them to detect regressions.

Quick Start

Run /canary https://example.com to start a 10-minute health check on the deployed URL.

Frequently Asked Questions about canary

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monitor a web app for production health after a deploy?

Post-deploy canary monitoring observes a live web app for production health by watching console errors, performance regressions, and page failures. You run a health check against a live URL to catch issues before users notice them.

What is a canary health check and how does it detect regressions?

A canary health check detects regressions by capturing baseline screenshots and comparing them against periodic live observations. It alerts on anomalies like page failures or new console errors found during the monitoring duration.

How do I start a canary health check on a deployed URL?

You start a canary health check by running the command with your target live environment URL. This initiates a default 10-minute monitoring session that browses pages, takes screenshots, and compares against baselines.

Can I configure the monitored pages and duration for post-deploy monitoring?

Post-deploy monitoring supports configurable duration and page sets. You can define which specific pages the browse daemon observes and set the monitoring window length to detect regressions quickly after your deployment.

Do I need a live environment to run canary monitoring?

Yes, canary monitoring requires a live environment to browse. The browse daemon must actively visit the deployed URL to take screenshots, compare against baselines, and alert on production anomalies.

What's the best way to catch performance regressions before users notice?

The best way to catch performance regressions early is automated post-deploy canary monitoring. It observes the live app using a browse daemon to compare current performance against generated baseline captures and alerts on anomalies.