Incident Lifecycle
The states an incident moves through from detection to resolution.
States
| State | Description |
|---|---|
| Active | The condition is currently detected by the agent. The incident is visible and actionable. |
| Resolved | The condition is no longer present. The incident is closed. |
| Dismissed | The condition was acknowledged as expected or non-actionable. |
State transitions
Active → Resolved
An incident moves to Resolved in two ways:
- Manual resolution — a team member clicks Resolve in the dashboard.
- Auto-resolution — if the agent stops reporting the condition (because the underlying issue was fixed), DataAgent automatically resolves the incident after 4 hours. See Auto-resolution.
Active → Dismissed
Dismiss an incident when the detected condition is expected and does not need investigation. Dismissed incidents are hidden from the default view but remain in history.
Examples:
- A pod restarted during a planned deployment
- A CronJob missed a run due to a scheduled maintenance window
- A resource is intentionally running at reduced capacity
Resolved / Dismissed → Active
If a resolved or dismissed condition is detected again in a future analysis cycle, DataAgent creates a new incident. It does not reopen the old one. This keeps incident history clean and makes recurrence easy to track.
Recurrence
If the same condition has occurred before, the incident detail view shows a recurrence count and links to prior incidents for the same resource.