SuperBizAgent-java/eval/rag-retrieval/seed-docs/incident-diagnosis-flow.md

title, keywords, summary, category, source, breadcrumb, kb_scope, covers, when_to_retrieve

title	keywords	summary	category	source	breadcrumb	kb_scope	covers	when_to_retrieve
Incident Diagnosis Flow	standard troubleshooting flow application incident collect evidence verify remediation	Standard flow for diagnosing application incidents with evidence, hypothesis verification, and remediation.	ops	incident-diagnosis-flow	AIOps > Diagnosis Flow	rag-eval	incident diagnosis evidence collection remediation	Use when the user asks for a standard troubleshooting flow or incident diagnosis sequence.

AIOps

Diagnosis Flow

The standard troubleshooting flow is evidence first, hypothesis second, remediation last.

Recommended sequence:

1. Collect evidence from alerts, metrics, logs, traces, deployments, and recent configuration changes.
2. Define a small hypothesis that explains the observed symptoms.
3. Verify the hypothesis with a targeted metric, log query, or reproduction step.
4. Choose remediation that directly addresses the verified cause.
5. Record the outcome and the evidence used to make the decision.

Do not skip collect evidence, verify, and remediation ordering during an application incident.