qa-synthetic-monitoring
Skill0 starsChanged 3 months agoMITView on GitHub
合成监控规格治理门禁技能:校验合成监控旅程规格是否「受治理」——业务关键旅程必须有断言(预期状态/文本)、告警阈值与探测频率;缺失则产出阻断信号,避免无断言/无告警的"哑"监控上线后漏报。触发词:"合成监控", "synthetic monitoring", "拨测", "探针", "黑盒监控", "监控门禁", or after qa-perf-analysis. 英文触发词(English triggers):synthetic monitoring, black-box monitoring, probe.
In this repository39 other files it gives its agents.
- qa-a11ySkill
- qa-agent-evalSkill
- qa-agent-securitySkill
- qa-api-contractSkill
- qa-api-docSkill
- qa-api-runnerSkill
- qa-archiveSkill
- qa-bug-reportSkill
- qa-bug-verifySkill
- qa-chaosSkill
- qa-ciSkill
- qa-code-reviewSkill
- qa-compat-matrixSkill
- qa-env-configSkill
- qa-executionSkill
- qa-exploratorySkill
- qa-flaky-detectSkill
- qa-mobile-autotestSkill
- qa-mutationSkill
- qa-orchestratorSkill
- qa-perf-analysisSkill
- qa-perf-designSkill
- qa-perf-jmeterSkill
- qa-perf-locustSkill
- qa-release-checkSkill
- qa-reportSkill
- qa-req-specSkill
- qa-risk-basedSkill
- qa-security-reportSkill
- qa-security-scanSkill
- qa-test-analysisSkill
- qa-test-case-genSkill
- qa-test-dataSkill
- qa-test-strategySkill
- qa-ui-automationSkill
- qa-ui-kbSkill
- qa-ui-testidSkill
- qa-unit-tddSkill
- qa-visual-regressionSkill
The file
Files
qa-synthetic-monitoring 合成监控治理门禁
用脚本化探针模拟用户关键旅程(登录、下单、支付),在受控环境持续探测以发现可用性 / 性能回归。本技能是一个治理门禁:它不实际对生产发起探测,而是校验你设计的合成监控规格是否「受治理」——业务关键旅程必须补齐断言、告警阈值与探测频率,否则视为"哑监控"(上线后既不报警也不验证),阻断发布。
⚠️ 治理门禁 · 不执行外部工具:本技能仅校验合成监控规格是否受治理,不实际对生产/线上发起任何探测;所有判定基于你提供的 YAML/JSON 规格,不做运行时拨测。
何时使用
- 你准备为关键用户旅程配置合成监控 / 拨测。
- 你写好了监控 YAML/JSON,想先卡一道「是否真能告警」的门禁。
- 在
qa-perf-analysis之后,或作为发布前线上可观测性保障的一环。
规则(治理三要素)
| 规则 | 含义 | 严重度 |
| SM-ASSERT | 每步须有断言(expected_status 或 expected_text) | 缺则 high;业务关键缺则 critical |
| SM-ALERT | 业务关键旅程须有告警阈值(alert_p95_s) | 缺则 high;业务关键缺则 critical/blocking |
| SM-FREQ | 旅程须有探测频率(frequency) | 缺则 high |
业务关键(business_critical: true)旅程缺断言或告警阈值 → 产出 blocking=true 信号,门禁失败。
使用方式
python qa-synthetic-monitoring/scripts/monitor_gate.py --spec monitor.json --out signals诚实边界(重要)
- 本技能只校验监控规格的治理完整性,不实际对生产 / 预发发起任何 HTTP 探测(无网络依赖)。
- 实际探测由黑盒监控 / ATS(如 Playwright 定时任务、云拨测)在受控环境执行;本技能确保「先治理、再上线」。
- 它不验证探测本身能否到达目标,只保证监控定义具备可告警的闭环。
参考资料
- 检查项、阈值、CLI 用法与常见坑:见
references/guide.md。
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

