10 lines
441 B
Markdown
10 lines
441 B
Markdown
|
# Incident Review Flow
|
||
|
|
|
||
|
|
When an incident occurs:
|
||
|
|
1. Identify the incident in the Dashboard or Events view.
|
||
|
|
2. Note the severity and the affected node/service.
|
||
|
|
3. Switch to the Events view to see the correlation chain.
|
||
|
|
4. Look for related events preceding the incident (e.g., latency spikes before a disconnect).
|
||
|
|
5. Check the Recommendations view for suggested fixes.
|
||
|
|
6. Once resolved, the incident will clear from the Active Incidents list.
|