Setup Alerts and Notifications

Alerts and Notifications

As of Device42 v15 and newer, the alerting engine has been completely re-written. Rules for alerts and notifications can be setup for the following objects in Device42:

  • PDU Sensors (individual humidity / temperature / … rules or any sensor rules)
  • PDU Infeeds (individual infeed rules or any infeed rules)
  • PDU Banks (individual bank rules or any bank rules)
  • Power Circuits (individual circuit rules or any circuit rules)
  • RF Code Sensors (tag group, tag type, individual sensor and any sensor rules)
  • Software License Counts (individual software, prohibited software, and any software rules)
  • Assigned Subnet Percentages (individual subnet and any subnet rules)
  • PDU Offline (PDU goes offline)
  • RF Code Timeouts

    Alerts and Notifications are governed by the same rules. When a rule triggers, an email alert is sent and a notification is created.

    To create alerts, navigate to Reports > Setup Alerts.

    To add an alert, click the Add button and you will see…

Create an Alert in Device42

To create a new alert, head to Reports -> Setup Alerts:

Alerts

In the example above, we’ve created a rule that will trigger an alert if any pdu bank goes over 80% of rated power. The rule will only trigger if the conditions persists for 180 seconds. If the condition still persists after 180 seconds, an email will be sent to both email addresses listed in the Action Email List (more than 2 addresses is also supported). Once the conditions clears, only sam smith will get an email indicating the condition cleared.

Then, if the alert is not acknowledged (see Notification Acknowledgements below) within 20 minutes (or whatever timeframe is specified), an escalation alert email will be sent to the emails in the Level1 Escalation List. Then, if the alert is not acknowledged within 120 minutes, another escalation alert email will be sent to the emails in the Level2 Escalation List. If no escalation emails are entered, no escalation alert emails will be sent.

An alert will not be repeated until after either:

  • Device42 has detected that the condition has cleared, or
  • The notification for the alert has been marked as cleared (see Notification Bulk Actions below)

Notifications

Once an alert triggers, it will be recorded in the Notifications List that can be found by navigating to Reports > Notifications

Notifications

Notifications will be present for all triggered alerts and additionally for notifications from other parts of the Device42 system such as from autodiscovery jobs. You will also see a Monitoring Appliance Timeout notification if a monitoring appliance is determined to be offline.

Customizing Alerts & Notification Variables (for POWER)

The new alerting engine offers powerful new alerting variables that allow configuration of custom alert emails that can be made to include useful data (e.g. the temp that caused the alert, power status, etc.).

The following variables are supported for embedding within alert emails when creating alerts for devices POWER-related devices like PDUs:

  • %(sensor_rule_id)s – Alert Rule ID
  • %(sensor_rule_name)s – Alert Rule Name
  • %(device_type)s – Device / PDU
  • %(device_name)s – Device name
  • %(device_id)s – Device ID
  • %(device_ip)s – Device IP
  • %(element_type)s – Infeed, output, bank, etc.
  • %(element_name)s – Name if available, if not – ID
  • %(element_id)s – Element ID
  • %(measure)s – Current/power, status, etc.
  • %(value)s – Value that triggered action
  • %(units)s – W(atts), Amps, etc.
  • %(status)s – Critcal/OK
  • %(remote_collector_id)s – RC ID
  • %(remote_collector_name)s – RC Name
  • %(date)s – Date when alert was triggered

You can use all tags in both message and subject like:

Alert %(sensor_rule_name)s triggered on RC#%(remote_collector_id)s

Bulk actions for alerts

Delete selected Notifications: Delete the selected notifications. If the condition recurs, a new alert and notification will be created.

Export selected items to CSV: Create a CSV file with the notifications.

Acknowledge alert: The purpose of this bulk action and of the corresponding Acknowledged column on this list page is to accomodate the case where multiple system administrators receive the alert. One system administrator can acknowledge the alert indicating that he/she is working on the issue.

Clear conditions: The purpose of this bulk action is to indicate to Device42 that the condition has been fixed and that a new alert and notification should be created if the condition recurs. Please note that only one notification will be sent until the condition is marked as cleared.

Supported Rule Types

RFCode rules can be defined for an entire RFCode Tag Group or Tag Type, an individual sensors, or any RF sensor. A rule can also be setup that defines what happens if the RFCode system is detected to be offline.

PDU infeed rules can be defined for individual infeeds or for all infeeds (e.g. if any infeed goes over the rated power limit). A rule can also be setup that defines what happens if a PDU infeed is detected to be offline.

PDU sensor rules can be defined for individual environmental sensors that are part of the PDU (e.g. a temperature or humidity sensor).

BCPM power circuit rules can be defined for an individual circuit or any circuit.

Subnet rules can be defined for individual subnets or any subnet.

Software license management rules can be defined for individual software components, any software component, or prohibited software components.