Closing event incidents
Set how many minutes without new events incidents from log errors, agents, and probes wait before closing on their own.
On this page
Log errors and findings from agents and probes don't signal when the problem ends. That's why their incident closes on its own after a period with no new events, and ARGUNIS sends the notification "resolved: no new errors in N min".
Before you start
Anyone can see the setting. To change it you need Administer on Core (Administrator role or a company role with that level).
Steps
Go to Core → Alarm policies.
Scroll down to Event incidents.
In Close after (minutes with no new events), type the time. It ranges from 5 minutes to 24 hours; the default is 30 minutes.
Click Save. To go back to the previous value, click Discard changes.
Below the field you see the current value and who last changed it.
How it behaves
If the service on the same component recovers, its error incident closes along with it once there are no new errors.
While it stays open and nobody takes it, it escalates like any incident, according to the group.
Security incidents close after 60 minutes with no activity; that time isn't changed here.
APM errors don't close with this window: they close after a new deployment without the error, after the APM thresholds' days without recurring (14 by default), or with Declare fix.