Multichannel notification and alert policies
Configure your rules so you only receive useful alerts!
Comprehensive notification policy parameters
We designed our notification system to offer a flexible choice of parameters so you can define your policies and rules exactly as you need.
. By server
Each server has its own notification policy that, by default, inherits notifications from all its sensors.
. By sensor
You can define a comprehensive notification policy for each sensor.
. By criticality
Choose whether or not an alert is triggered depending on the incident’s criticality. Specify at what times alerts will be triggered: when an incident occurs, when it is resolved, every X minutes while the situation remains, etc.
. By time range
Set different rules for time ranges depending on your services’ criticality. Cater for your maintenance periods and special days (public holidays, etc.). Don’t be disturbed on a Sunday because an office printer server is down!
. By user
Users are not always affected by every incident, or they want to receive the minimum number of alerts. For example, operational teams want to receive an alert at each step in the incident management cycle, whereas managers will receive only two device alerts (when an incident is reported and when it is closed).
Multichannel alerts: be informed any time, anywhere!
Alerts are sent through different channels, as you choose.
. In the portal
. By email
. By instant messaging
. By social networking
iPhone push alerts
Receive alerts discreetly in your pocket, thanks to iPhone push notification.
You can also set whether or not you want to receive alerts, directly from your iPhone, to deactivate push alerts during a meeting, during your hours of sleep, etc.
You can choose to receive SMS alerts.