- 20 Sep 2023
- 2 Minutes to read
Host Alert Contact
- Updated on 20 Sep 2023
- 2 Minutes to read
Host alert contacts provide Netreo with a means of alerting appropriate personnel when any given host fails its availability service 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 host alert contacts may share the same escalation tier). (Escalation tiers are sometimes called "Alert Thresholds" in the interface.)
The configured host alert contacts for any given device may be viewed in the administrative view of its Device Dashboard. The configured host alert contacts for groups of devices can be viewed using the "Configured Alerts" report (Reports > Alerts > Configured Alerts in the main menu).
Host alert contacts may only be configured and assigned by a user with the Admin access level or higher.
It is important to note that host alert notifications follow a different escalation convention than that used for other service and threshold checks. Host alert notifications are sent based on escalation tier levels (see table below), allowing you to specify at exactly what escalation level specific people will receive alerts. When an incident is opened due to a failed availability service check, the incident checks the "Host Alert Contacts" table of the respective host device and attempts to send its first alert notification to all tier 1 members. After the "RENOTIFY INTERVAL" (specified in the "Alerting" section of the administrative view of the device's Device Dashboard) 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. Until the incident is acknowledged or closed, this process continues until it reaches tier 10. At that point, all tiers will continue to receive alerts 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 have already been 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 have already been 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 when devices are discovered via device templates (which is the recommended method).