synthetic-monitoring
Catch broken user journeys after your release.
What it does
Guides the creation of continuous production probes, actionable alerts, and reliability tracking for critical user journeys.
When to use it
Use for continuous synthetic monitoring, scheduled probes, availability monitoring, and SLA validation after deployment, rather than a one-shot release gate.
How to use it
Give it an application to monitor; it produces probes, alerting configuration, reliability tracking, and per-probe runbooks.
What you provide
- An existing project
Uses
Good to know
- cannot be undone: PagerDuty; Slack
What you need · 2
Production probes require dedicated synthetic accounts with stable test data, excluded from analytics, billing, campaigns, and reliability pipelines.
Authenticated probes use test-account credentials supplied through process.env from a secrets manager; the instructions require quarterly rotation.
Access · 5
This skill
PagerDuty
Pages on-call through PagerDuty (irreversible)
Slack
Sends incident and monitoring alerts (irreversible)