28 lines
1.1 KiB
Markdown
28 lines
1.1 KiB
Markdown
---
|
|
title: Incident Diagnosis Flow
|
|
keywords: [standard troubleshooting flow, application incident, collect evidence, verify, remediation]
|
|
summary: Standard flow for diagnosing application incidents with evidence, hypothesis verification, and remediation.
|
|
category: ops
|
|
source: incident-diagnosis-flow
|
|
breadcrumb: AIOps > Diagnosis Flow
|
|
kb_scope: rag-eval
|
|
covers: [incident diagnosis, evidence collection, remediation]
|
|
when_to_retrieve: 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.
|