In the Alerts section of a device you can easily configure alerts for a device.
Domotz offers flexible mechanisms to configure predefined sets of alerts for your account or team and for systems you are integrated with.
Personal Alerts
These are alerts that will be notified only to your account (via email or mobile push notification). Each user can have their own personal alerts.
To simplify the setup of alerts, Domotz allows you to quickly assign to a device one these options:
- No Alerts (default).
- Standard Alerts: to assign a predefined set of alerts that you can configure once, and assign to all the devices you want.
- Custom Alerts: to assign a specific set of alerts to the device. Available alerts will depend on the type of devices and the services it offers.
Standard Alerts
Standard Alerts are particularly useful if you want to reuse the same set of alerts on a number of devices. In this case, you can select Standard to have them applied to the device.
In order to modify the predefined set of standard alerts, just click on the Edit Standard Profile button.
Please note that the Standard alerts only includes a limited choice: the types of alerts that are applicable to any IP device.
Custom Alerts
With the Custom Alerts option, you can assign a distinct set of alerts tailored to that device. Available alerts will depend on the type of the device as shown in the example below.
Shared Alerts
You can configure events to be sent to your preferred contact channel. A contact channel can be a PSA or ticketing system, a webhook, an integrated system, or a distribution list of email addresses. For instructions on creating a Shared Alert profile, please refer to Shared Alerts, Webhooks, and Ticketing Systems.
When you sign up for Domotz, your account is automatically created with a default Device Monitoring Shared Alert profile, configured using your email address as the contact channel.
This profile includes the following events:
- Device Goes Up
- Device Goes Down
- IP Change
- TCP Events
- Configuration Change
- Configuration Misalignment
A Shared Alert profile can be easily assigned to a device. Simply click the Add Shared Alerts button and select one of the available Shared Alert profiles, as shown in the example below.
Types of Device Events
A device alert is triggered by a connectivity-related event and generates a notification.
Below is the list of device events available in Domotz:
Device Goes Down
Triggered when the device remains offline longer than the configured Offline Threshold (default is 2 minutes, equivalent to 4 consecutive missed heartbeat checks).
Device Goes Up
Triggered as soon as the device comes back online.
Heartbeat Lost
Triggered when a device misses a heartbeat. A heartbeat check consists of a train of ICMP or ARP pings sent every 30 seconds, depending on whether the monitored device resides on a Layer 2 (directly attached network) or Layer 3 network (Routed Networks).
IP Change
Triggered when a device changes its IP address.
Connection Performance / Ping RTD
You can set the system to trigger if there is a connection performance issue.
The Domotz agent periodically sends packets to all devices in the network and keep track of Response Time Delay and packet loss (more details in Device management Overview ).
You can configure:
- A median latency limit (event is triggered if RTD goes above that limit).
- A packet loss % limit (event is triggered if the packet loss % goes above that limit).
TCP Services events
Triggered if a TCP service of a device goes Up or Down.
Please refer to TCP services Monitoring for more details.
If you are going to setup a shared Alert for TCP sensors please see: https://help.domotz.com/user-guide/custom-snmp-alert/
SNMP Sensors events
Triggered if the value of an SNMP sensor that you have configured meets certain conditions.
Please refer to SNMP and TCP services Monitoring for more details on how to configure SNMP Sensors and related alerts.
Feature Discovery
Triggered if Domotz has discovered a new capability on one of the device on the network offers new capabilities that can be exploited by Domotz. For example if a device has been discovered with additional MIB library.
Please refer to Feature Discovery Event for more details about this type of event and how it can be used on WebHooks to automate the mechanism.
