Auto-Resolution

How it works

When an agent fixes a condition (for example, a crashing pod is restarted and stabilises), it stops reporting that condition’s signal hash in subsequent analysis cycles. DataAgent detects the absence of the signal and automatically resolves the incident after 4 hours.

This means your team does not need to manually resolve every incident — conditions that fix themselves are closed automatically.

Timeline

T+0m   Condition detected → incident created (Active)
T+5m   Condition still present → last_seen updated
...
T+Xm   Condition no longer present → agent stops reporting the signal
T+X+4h No signal reported for 4 hours → incident auto-resolved

When auto-resolution does not trigger

Auto-resolution requires the agent to be connected and sending heartbeats. If the agent is offline, DataAgent cannot confirm the condition is gone and will not auto-resolve.

In this case, resolve the incident manually once the issue is confirmed fixed.

Recurrence

If the same condition is detected again after an incident is resolved — whether manually or automatically — DataAgent creates a new incident. It does not reopen the old one.

The new incident’s detail view links to prior incidents for the same resource so you can see the recurrence history.