DocumentaciónHelp

Alarm policies

Decide what ARGUNIS does with each alarm before opening an incident, when event incidents close, and how outages are correlated.

On this page

An alarm policy decides what ARGUNIS does with an alarm before opening an incident:

Action

What it does

Incident

Opens an incident and notifies, with optional threshold and duration

Event only

Stays in Events, with no incident or notification

Ignore

Not even an event: it only adds to the policy's ignored counter

With no policies, every alarm opens an incident and notifies, as usual.

How the policy is chosen

The most specific one wins: an asset, then an inventory group (and its parent groups, from nearest to farthest), then a source type and, finally, the condition alone. Among equally specific policies, the one with the highest priority wins.

On the screen

In Core → Alarm policies you see the policies table with their Level, Scope and condition, Action, how many alarms it Applied to (and the last time), the Priority, and its Status. Further down are the simulator and two company settings: closing event incidents and dependency correlation.

Pages

Search Argunis Monitoring

Type at least 2 characters to search Argunis Monitoring.

↑↓ to navigate · Enter to open · Esc to close