Metrics Anomaly Analysis: Use anomalous metrics to locate the time window, impact, and candidate causes
An alert threshold firing does not automatically mean an incident. Seasonality, traffic shifts, and sampling bias can all create anomalies. Metric analysis must first distinguish signal, baseline, and business impact.
The Metrics Anomaly Analysis Skill tests an apparent spike against history, correlated indicators, and user impact before turning it into an operational conclusion.
This guide uses concrete scenarios to show how to collect, connect, and interpret evidence so the conclusion can support the next engineering or business decision.
Metrics Anomaly Analysis Skill: what it is for
Metrics Anomaly Analysis is for work that needs a clear, handoff-ready testing judgment. It keeps project material, the basis for each decision, and the next action on the same trail—so a reader can see what to inspect before choosing how to execute and review it. This guide works through one concrete scenario and keeps human decision boundaries visible.
Start with the source Skill
The complete execution contract lives in Metrics Anomaly Analysis prompt. The source directory also contains 3 evaluation cases for checking whether an output follows the contract.
The entry point calls out these constraints:
- do not infer causation from synchronized movement alone
- validate metric definitions and collection gaps
- distinguish statistical from business anomalies
Begin with project facts
Put the material you have on the table. Gaps may remain; their status needs to stay explicit.
| Material | What to provide | What to do when it is missing |
|---|---|---|
| Goal and scope | Investigate checkout-success and latency anomalies by validating the window, metric definition, impact scope, and candidate causes | Name journeys outside this pass |
| Version and environment | Requirement version, build, environment, time window | Stay in design or analysis mode |
| Evidence | Requirements, interfaces, logs, metrics, traces, or defects | Separate facts, assumptions, and open questions |
| Decision boundary | Risk approver and actions that are not authorized | Name the owner and next step |
Use a request like this:
Use the metrics-anomaly-analysis Skill.
Task: Investigate checkout-success and latency anomalies by validating the window, metric definition, impact scope, and candidate causes
Inputs: [versions, links, log paths, or reports]
Scope: [included and excluded objects]
Constraints: [time, data, permissions, compliance]
Audit the inputs first. Order results by risk and evidence strength. Label unsupported claims as assumptions and give a validation method.Make the result usable by the next person
| Output field | Why it exists | Example status |
|---|---|---|
| Finding or judgment | Describes observed behavior, difference, or risk | Confirmed / Assumption / Open |
| Basis | Points to a version, log, trace, test, or requirement | source_id or link |
| Impact | Explains affected users, journeys, or release decision | P0, P1, or accepted residual risk |
| Next action | Names verification work and an owner | Owner, date, expected evidence |
Do not write “passed” without a run record, query result, or source artifact. Static analysis and runtime proof are different things.
Run one focused pass
Start with a bounded pass—Investigate checkout-success and latency anomalies by validating the window, metric definition, impact scope, and candidate causes. Put the input version, time window, and accountable owner in one place. Then link each judgment to an artifact. Finish with one validation action that can change the decision.
Rule out collection and definition changes before business causes; label evidence strength for every hypothesis. The handoff should include an evidence index, assumptions that still need checking, and an action the next person can run without reconstructing the conversation. Plain work. It holds up.
Run one focused pass
Start with a bounded pass—Investigate checkout-success and latency anomalies by validating the window, metric definition, impact scope, and candidate causes. Put the input version, time window, and accountable owner in one place. Then link each judgment to an artifact. Finish with one validation action that can change the decision.
Rule out collection and definition changes before business causes; label evidence strength for every hypothesis. The handoff should include an evidence index, assumptions that still need checking, and an action the next person can run without reconstructing the conversation. Plain work. It holds up.
Advanced use: turn one analysis into a maintained mechanism
Rule out collection and definition changes before business causes; label evidence strength for every hypothesis.
Keep input versions and source IDs with every result. When requirements, code, environment, or data change, recompute only affected judgments and mark them changed, unchanged, or needs-review. Old conclusions are not new evidence.
A three-Skill chain
metrics-anomaly-analysis → distributed-trace-analysis → production-incident-analysis
| Handoff | Payload | Receiver check |
|---|---|---|
| Upstream to metrics-anomaly-analysis | Source versions, scope, risk, open items | Staleness and conflicts |
| metrics-anomaly-analysis to downstream | Judgments, evidence index, residual risk, tasks | Executability and ownership |
| Feedback to metrics-anomaly-analysis | Runs, defects, changed facts | Baseline and regression scope |
Hand over a summary, an evidence index, and locations for the source artifacts. That gives the receiver enough context and keeps the trail recoverable.
Team gates
| Gate | Check | Failure action |
|---|---|---|
| metrics-anomaly-analysis input | Version, environment, sources, and owner | Stop and list gaps |
| metrics-anomaly-analysis artifact | Material claims have basis, status, and impact | Return for evidence |
| metrics-anomaly-analysis execution | Command, query, or verification path is repeatable | Classify infrastructure or test issue |
| metrics-anomaly-analysis decision | Residual risk has an accepter and date | Do not enter the next stage |
Common traps
- Listing checks without input conditions, expected results, or evidence.
- Marking every finding high priority and removing the team’s ability to choose.
- Refusing to produce a bounded first pass, or presenting guesses as facts.
- Treating one success or one anomaly as long-term behavior while ignoring repeated trials and version changes.
Two practical questions
Can I start with incomplete input?
Yes. Produce a constrained first pass with known facts, assumptions, gaps, and the smallest validation action. Missing environment, data, or permission cannot support an execution claim.
When is human confirmation required?
The accountable owner must confirm scope trade-offs, risk acceptance, production actions, data permission, and release decisions. The Skill organizes evidence and options; it does not grant authority.
Run Metrics Anomaly Analysis with one real artifact and keep the input, output, human edits, and verification evidence in the same work chain. That is what makes the next change cheaper to assess.
References
- Metrics Anomaly Analysis prompt:https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/metrics-anomaly-analysis/prompts/metrics-anomaly-analysis.md
- Awesome QA Skills: Metrics Anomaly Analysis Skill source:https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/metrics-anomaly-analysis
- Awesome QA Skills on GitHub:https://github.com/naodeng/awesome-qa-skills
- Metrics Anomaly Analysis Skill details:https://inaodeng.com/en/qaskills/metrics-anomaly-analysis/