1. Home
  2. OmniCenter Reference
  3. Alert Notifications

Alert Notifications

Example of an email notification.

An alert notification is OmniCenter’s way of remotely alerting appropriate personnel to a critical problem with your network. These notifications come in the form of a plain-text-based message sent via email, SMS or mobile push. It indicates that an OmniCenter check is experiencing an alarm (typically indicating a critical condition) and has opened an incident. The basic process is:

  • An OmniCenter check assigned to a device experiences a CRITICAL state (or for some service checks, a WARNING state).
  • OmniCenter generates an alarm for that check. (Alarms display in the dashboards.)
  • The alarm attempts to open an incident associated with that device.
  • The contact/action groups assigned to the respective check during its configuration assign those groups to the incident.
  • The incident attempts to send alert notifications based on the contact/action groups assigned to it.
Example of a mobile push notification.

See the Incident entry for a more in-depth explanation of this process.

The form an alert notification takes is dependent on the alert template used for a given incident type. OmniCenter provides many alert templates by default. However, administrators can create additional custom alert templates to suit their environment.

An alert is not the same thing as an alarm. An alarm is an event experienced by an OmniCenter check which causes an incident to be opened, an alert tells you about that incident.

OmniCenter is generally configured to send alert notifications via email. Our best practice recommendation is to allow OmniCenter to communicate outbound to the Internet on port TCP/25, as this allows direct connections to smartphone gateways from which you may want to receive alerts. If that access is not possible, you can relay SMTP mail through an internal server, however this creates a single point of failure for alerts if that relay host stops responding, so we recommend this configuration only as a last resort (or for testing purposes).

In order to send alerts to the OmniCenter Mobile app, or to use webhooks to integrate OmniCenter notifications with external services like Slack, OpsGenie, PagerDuty, or ServiceNow, you will have to allow the OmniCenter server to have outbound (Internet) access on port TCP/443.

To create and configure alert notification templates, see Alert Template Admin.

Updated on July 10, 2019

Was this article helpful?

Need Support?
Can’t find the answer you’re looking for? Don’t worry we’re here to help!
Contact Support

Leave a Reply