synthetic-monitoring
能在低流量时发现问题，适合 SRE/运维与 QA 团队。
需要对生产环境持续访问与警报配置，涉及权限与误报风险。
在生产上定时运行脚本化探针，持续检测关键用户流程与可用性。
在生产持续定时跑脚本化探针，24/7 检测关键用户流程、可用性和 SLA，能够在凌晨流量为零时也发现故障或性能退化。它涵盖探针设计、多区域监控、告警集成和 SLA 验证，适合上线后做持续可用性保证，不用于替代发布时的安全放量或从生产遥测直接设计测试。
▸ 展开 SKILL.md 英文原文
Scheduled probes that run CONTINUOUSLY after release. Covers probe design for critical user journeys, alerting integration, SLA validation, multi-region monitoring, and the boundary between QA and SRE. Use when: "synthetic monitoring," "uptime testing," "scheduled probes," "SLA validation," "availability monitoring," "post-deploy checks." Not for: safe-release techniques during rollout — use testing-in-production. Not for: designing tests from prod telemetry — use observability-driven-testing. Not for: a one-shot post-deploy smoke gate tied to a release — use release-readiness. Related: testing-in-production, release-readiness, performance-testing, qa-metrics.
帮我安装这个 skill：https://raw.githubusercontent.com/petrkindlmann/qa-skills/main/skills/synthetic-monitoring/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/petrkindlmann/qa-skills/main/skills/synthetic-monitoring/SKILL.md"<objective> Synthetic monitoring runs scripted tests against production on a schedule, 24/7. It catches outages, performance degradation, and broken flows before real users report them — at 3 AM when traffic is zero, probes are the only thing checking your app works. A login page that always returns 200 but never authenticates passes a naive uptime check; a synthetic probe that asserts the dashboard loads catches it. This skill covers probe design, alerting integration, SLA validation, multi-region execution, and the runbook discipline that keeps a 3 AM page actionable. </objective> ## Quick Route | Situation | Go to | |-----------|-------| | Picking a platform (Checkly, Datadog, Grafana,