Alerts and Notifications
You can set up Device42 Alerts to notify you about application, asset, software, discovery, and other conditions that affect your IT environment. Alerts can generate notifications within the Device42 UI or be integrated with external systems such as PagerDuty, Opsgenie, etc.
As of v16.14.00, Device42 has refined and improved its Alerts functionality.
Set Up Alerts
To create an alert, select Analytics > Setup Alerts from the Device42 menu bar and then click Add Alert on the Select Alert to view page.
- Enter a Name for the alert, and then select the Rule Type for the alert. Each Rule Type has associated Triggers, which define the conditions that will generate an alert.
- Select the Trigger you want for the Rule Type you selected.
- Select the Alert Type.
- If you select D42 Notification, select or add the Escalation Profile to use for the alert. You use Escalation Profiles to set up email notification escalation tiers. Select Tools > Admins & Permissions > Escalation Profiles to add or edit escalation profiles.
- If you select Alert Integration, select or add the alert integration (for example, PagerDuty, Opsgenie, etc.) to use for the alert. Select Tools > Integrations > External Integrations to view or add external integrations. Also see https://www.device42.com/integrations/ for more information about Device42 integrations.
As you construct your alert, Device42 displays the alert definition based on the options you select or enter. The example below shows an Operating System Count alert that sends a notification to the Alert Group 1 escalation profile.
Depending on the alert Rule Type you select, you may also see an Apply To: option that you use to select the objects you want to apply the alert to. Use the Available objects list on the left to select the objects you want to add to the Chosen objects list on the right.
- Priority — Critical, High Priority, Medium Priority, Low Priority
- Resend Notification — Amount of time (in seconds) to wait before sending an email notification for the alert. Leave this field blank to send the email only once.
- Seconds Before Action — Amount of time (in seconds) that the alert condition (the trigger) exists before the Device42 generates the alert.
- Notes — Any notes about the alert.
- Notification Template — Text fields you can use to create templates for the Subject and Message of the alert email.
When you are done, click Save at the bottom of the page to save the alert.
Alert Rule Types and Triggers
- New Affinity Group Dependency Found
- Affinity Group Dependency Removed
CRAC (Computer Room Air Conditioner)
- Inlet Temperature
- Return Temperature
- Scan Alerts
- Power Circuit Mismatch
- Job failed to start, because it’s still running
- Job failed to start, because system experienced a problem
- Job failed to start on time
- License Percent used
- Number Available
- % Available
- Avg Watts
- Avg Current
- Avg Volts
- Is Offline
- Is Not Responding
- Bank Power (A)
- Bank % of Rated Power (A)
- Infeed Power (A)
- Infeed % of Rated Power (A)
- Sensor humidity (percentage)
- Sensor temperature (fahrenheit)
- Sensor temperature (celsius)
- License Percent Used
- Prohibited Software Installed
- Percent Used
- Days Until License Expiration
- Percent of Licensed devices
- Percent of Licensed IPs
- Any Remote Collector Disconnected
- Any WDS Disconnected
- Battery % Capacity Remaining
- Battery Time Remaining
- Actual Voltage
- Actual Current
- Load %
- A Battery is Low
- A Battery is Depleted
- A Battery Needs Replacing
- A Battery Has a Fault
If you select D42 Notification as the Alert Type when you create an alert, Device42 generates a notification when the alert condition triggers the alert. Device42 adds all notifications to the Notifications page.
The Device42 Dashboard now includes two links – My Notifications and All Notifications – to the Notifications page, and there is a bell icon in the menu bar that animates when you receive new notifications. You can hover over the icon to see a list of recent notifications or jump the the Notifications page.
You can also select Analytics > Notifications from the menu bar to go to the Notifications page.
The page displays notifications for all triggered alerts whose Alert Type is Device42 Notification. Click My Notifications or All Notifications to see the notification lists.
Select the alerts you want and select the Action drop-down menu to perform the following action on the notifications
- Delete selected Notifications – deletes the notification. If the condition reoccurs, Device42 generates a new notification.
- Export selected items to CSV – create a notification CSV.
- Acknowledge Alerts – acknowledge the alert that generated the notification. Any alert recipient can acknowledge alerts.
- Clear Conditions – clear the alert condition that generated the notification. This indicates that the condition has been fixed and Device42 will generate a new alert and notification if the condition reoccurs. Note that only one notification is sent until the condition is marked as cleared.
Customizing Power-related Alerts 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.).
Device42 supports the following variables for embedding within alert emails when creating power-related alerts.
- %(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 — Watts, Amps, etc.
- %(status)s — Critical/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