Setup Alerts and Notifications

Alerts and Notifications

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

  • Device42 license – days to license expiration
  • Individual Power Unit Sensor(s) – temperature / humidity rules for selected sensors
  • Any Power Unit Sensor – temperature / humidity rules for any sensor
  • Individual Power Unit(s) Infeed – power threshold rules for selected power unit infeeds
  • Any Power Unit(s) Infeed – power threshold rules for any power unit infeed
  • Power Unit Offline – any power unit gateway is offline
  • Individual Bankpower threshold rules for selected PDU bank(s)
  • Any Bankpower threshold rules for any PDU bank
  • Any UPSstate / threshold rules (battery, voltage, current, load) for any UPS
  • Individual Software Countcount / license percentage use for selected software / OS(s)
  • Any Software Countcount / license percentage use for any software / OS
  • Prohibited Softwarewhen any prohibited is discovered
  • Individual Operating System Count count / license percentage use for selected OS(s)
  • Any Operating System Count count / license percentage use for any OS
  • Individual Subnet percentage use for individual subnet(s)
  • Any Subnet percentage use for any subnet
  • Individual Part Model Countnumber / percentage available for selected part model(s)
  • Any Part Model Count – number / percentage available for selected part model(s)

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

Create an Alert in Device42

To create an alert, select Reports > Setup Alerts, and then click Add Alert at the top right of the page.

In the example above, we’ve created a rule that will trigger an alert if any power unit bank goes over 80% of rated power. The rule only triggers if the conditions persists for 180 seconds; at that point, an email is sent to both email addresses listed in the Action Email List (separate multiple addresses with commas).

Then, if the alert is not acknowledged (see Notifications below) within 20 minutes (Resend Minutes), an escalation alert email will be sent to the emails in the Level 1 Escalation List. If you do not enter Escalation Level email addresses, no escalation alert emails are sent.

The alert will not be repeated if:

  • Device42 detects that the condition has cleared, or
  • The notification for the alert has been marked as cleared (see Notifications below).


Once an alert is sent, it is added to the Notifications list; select Reports > Notifications to see all notifications.

Notifications are displayed for all triggered alerts (and also for other Device42 functions such as autodiscovery jobs). The illustration above shows PDU Infeed notifications.

Using the Notifications drop-down menu you can:

  • Delete notifications. If the condition recurs, a new notification is created.
  • Export notifications to a CSV file.
  • Acknowledge the alert(s) that generated the notification(s). Any alert recipient can acknowledge alerts.
  • Clear the conditions of the alert(s) that generated the notification(s). This indicates that the condition has been fixed and that a new alert and notification should be created if the condition recurs. Note that only one notification is sent until the condition is marked as cleared.

Customizing Alerts for Power Devices with Notification Variables

The new alerts engine offers powerful new alerting variables that let you configure custom alert emails that can include useful data (for example, the temperature that caused the alert, device power status, etc.).

The following variables are supported for embedding within alert emails when creating alerts for power-related devices .

  • %(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 the tags in both the alert message and subject line:

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