Error Rate Monitor Skill for Low-Traffic Alerts
Define error-rate numerators, request denominators, and minimum traffic thresholds so alert decisions are reproducible.
中文Install in Claude Code
Use your own service or synthetic counters. Define the request window, included 5xx responses, and exclusions.
- Get the complete `plugins/performance/error-rate-monitor/skills/monitoring-error-rates` directory from the pinned GitHub commit.
- Copy it into the target project's `.claude/skills/`. Check `.claude/skills/monitoring-error-rates/SKILL.md`, start Claude Code at the project root, and call `/monitoring-error-rates`.
Example task
Compare window A with 1 failure in 2 requests and B with 30 failures in 100. Use an example threshold above 20% and at least 20 total requests.What to check
A has 50% and B has 30%, but only B alerts under the stated rule. Keep both raw counts in the report.
Original SKILL.md on GitHub · Updated
Frequently asked question
Should an empty request window be reported as a zero error rate?
Mark it as no traffic or insufficient observations to avoid mistaking missing measurements for healthy traffic.