Host alert contacts provide OmniCenter with a means of alerting appropriate personnel when any given host fails a host check. Each host alert contact consists of one action group and an escalation tier number that determines when host alert notifications are sent to the members of that group.
There are 10 escalation tiers available (1 through 10). Any number of host alert contacts may be added to a device at any tier level, but each host alert contact may only contain one contact or action group (although multiple contacts may share the same escalation tier).
The configured host alert contacts for any given device may be viewed in its administration dashboard. The configured host alert contacts for groups of devices can be viewed using the “Configured Alerts” report.
Host alert contacts may only be configured and assigned by an administrator. They are managed in the device administration dashboard for any given device. See the entries for device administration dashboard for more information.
It is important to note that host alert notifications follow a different escalation convention than that used for other OmniCenter checks. Host alert notifications are sent based on escalation tier levels (see table below). When an incident is opened due to a failed host check, it checks the “Host Alert Contacts” table of the respective host device and attempts to send its first alert notifications to all tier 1 members. After the “RENOTIFY INTERVAL” (specified on the “Alerting” administration page for the device) has passed, the incident will then attempt to send alert notifications to all tier 1 and tier 2 members. After the “RENOTIFY INTERVAL” has passed again, the incident will then attempt to send alert notifications to all tier 1, tier 2, and tier 3 members. Unless the incident is acknowledged or closed, this process continues until it reaches tier 10. From that point on, all tiers will continue to be renotified until the incident is either acknowledged or closed.
|1||0||Tier 1 members receive the first alert notifications to go out, as well as all subsequent alerts.|
|2||1||When the first RENOTIFY INTERVAL has passed (meaning that tier 1 members are being renotified), tier 2 members also begin receiving alert notifications.|
|3||2||As above, but with tier 3 members.When the second RENOTIFY INTERVAL has passed (meaning that tier 1 and tier 2 members are being renotified), tier 3 members begin receiving alert notifications.|
|4||3||As above, but with tier 4 members.|
|5||4||As above, but with tier 5 members.|
|6||5||As above, but with tier 6 members.|
|7||6||As above, but with tier 7 members.|
|8||7||As above, but with tier 8 members.|
|9||8||As above, but with tier 9 members.|
|10||9||As above, but with tier 10 members. From this point on, all tiers will continue to be renotified until the associated incident is either acknowledged or closed.|
Host alert contacts can be added to devices automatically via device templates (the recommended method). See the entry for device templates for more information.