We’ve just released exciting new features on Domotz, including alerts on SNMP sensors, OS monitoring sensors, and custom integration drivers, which many of you have been waiting for. Exciting new features this month include a more powerful alerting mechanism for the following SNMP sensors:
Read on to learn about all the new functionalities we’ve released in the last few weeks. In summary, here’s what’s new on Domotz this month.
- More advanced and powerful alerts
- Integration with make.com (formerly Integromat)
- Additional scripts for monitoring Kubernetes
- Improvements to External Host monitoring
- Enhancements to the Sites Explorer
- Support for multiple Customers in the Syncro Integration
- Custom Integration Drivers list via Public API
- Additional MIBs
What’s new
More advanced and powerful alerts
You can now set alerts on the following sensors:
These new features rely on a new mechanism for alerting, which is more powerful. This new mechanism allows you to configure more sophisticated alerting rules.
Setting Alerts for Printer Supply Levels
1. Navigate to the "Device Details" page for the HP 6970 Printer. Confirm the printer is online with an IP address of 10.0.0.17.
2. Under the "SNMP Monitoring" section, ensure the status is "READ" and monitor the "Printer Supplies Table."
3. To set an alert, locate the "Set an alert on Supply Level" pop-up. There are options for "Supply Level Low" set at less than or equal to 30%, and "Supply Level VERY Low" set at less than or equal to 10%. Use these settings to receive alerts when supplies reach these levels.
4. Use the "Add Pre-configured SNMP Sensors" button for additional sensor configurations.
5. Check the "Actions" menu on the right for options to apply drivers, export, or import device settings.
6. Review recent logs in the activity section, including device status changes and IP changes.
A more powerful alerting mechanism
Thanks to our new alerting mechanism, you can receive an alert for the different metrics on different contact channels. For instance, receive an alert on a specific Contact Channel if a metric breaches a certain threshold. Moreover, you can receive a different alert, for instance, on a different Contact Channel, if a metric breaches a different threshold. Our new alerting mechanism offers you greater flexibility in creating alerts for the metrics you care about.
Moreover, you can also easily apply and re-use the same alert profile for the same type of sensor:
Set an Alert on Supply Levels
1. Select "Supply Level VERY Low" to set an alert for when levels are less than or equal to 10. Click "Edit" to modify this alert or check the box to activate it.
2. Choose "Supply Level Low" for alerts when supply levels are less than or equal to 30. Use the checkbox to enable this alert.
3. Click "Configure new alert" to create a custom alert with different parameters.
4. Options for alert notifications include icons for various alert types like email or platform notifications.
Similarly, if you edit an existing Alert Profile, all the sensors using that Alert Profile will inherit that change too.
Each Alert has an internal state (depending if the condition to trigger the notification is met or resolved). If you connect an external Ticketing System to Domotz, the tickets will update and resolve automatically if the auto-resolve functionality is available.
Similarly, when receiving messages on the chat channel (Telegram, Slack, Microsoft Teams) of your preference, we’ll highlight the status of the trigger in the message itself. For example, below is an alert example of when a particular sensor’s value breaches the alert condition:
Alert Notification for Estimated Remaining Minutes
1. An alert is triggered with the status "Problem" indicating that the estimated remaining minutes exceed thirty-one.
2. The alert applies to the device "UPS-RLINKCARD.Ian" located at "St John's High School - Draper."
3. The current condition shows that the remaining minutes are greater than 31, with an actual value of 32 minutes.
4. Two actionable buttons are available: "View Agent St John's High School - Draper" and "View Device UPS-RLINKCARD.Ian." Use these to access the agent or device for further investigation or resolution.
And this is when that same value returns within the acceptable range:
Notification of Resolved Alert in Domotz
1. A resolved alert regarding "Estimated Remaining Minutes" is displayed, indicating the duration was higher than thirty-one minutes.
2. The alert applies to the device UPS-RLINKCARD.lan at the site "St John's High School - Draper."
3. Current Status is marked as Resolved.
4. The Alert Name is specified as "Estimated Remaining Minutes higher than thirty one."
5. The condition triggering the alert was “greater than 31.”
6. The Current Value at the time of resolution was 31 minutes.
7. The Identifier for the alert is "Estimated Remaining Minutes."
8. Two buttons are available: "View Agent St John's High School - Draper" and "View Device UPS-RLINKCARD.lan."
You can configure your alerts in the relevant tab of the Device Details section (i.e., SNMP tab for the PreConfigured SNMP Sensors, Drivers tab for the Custom Integration Drivers, and System for the OS Monitoring ones):
Setting Alerts for SSL Certificate Expiry in Domotz
1. On the "Device Details" page for the Domotz Website, navigate to the "Drivers" tab.
2. Under "Custom Integrations," select "Bulk SSL Certificate Validity." The status should indicate "RUNNING."
3. In the "Set an alert on Remaining days" pop-up, configure alerts:
- To set a "SUPER URGENT" alert, check the box next to "is less than 10."
- For a "Certificate Expiring" alert, ensure "is less than 45" is checked.
4. Use "Configure new alert" to add additional alerts if needed.
5. Review the "SSL Certificates" section to monitor expiry dates and set alerts accordingly.
Moreover, you can also configure these new alerts in the Monitoring Tables of the custom Dashboards:
Alert Configuration for Network Interfaces
1. Navigate to the "New Alerts" section in the monitoring dashboard.
2. Locate the table displaying network interfaces. Key columns include Site Name, Device Name, Interface, IP Address, Status, Operational Status, Inbound Traffic, and Inbound Errors/s.
3. In the "Alert Configuration" panel, set the alert name to "Inbound Traffic too high."
4. Under "If the value is," choose "Is Greater Than" and enter "10000" in the byte/s field.
5. Select the option to send an event notice to the specified ticketing system, "HaloPSA."
6. Use "Add contact channels" if additional notification methods are required.
7. Click "Add" to save the alert configuration or "Cancel" to discard changes.
By enabling you to configure these alerts from the monitoring dashboard, you can now configure the same type of alert on the same type of variable across multiple devices and sites/networks:
OS Monitoring Dashboard with Memory and Operating System Sections
1. The top section displays a list of monitored devices, showing details such as site name, device name, type, IP address, status, memory used, and physical memory.
2. Memory usage is indicated in percentages, alongside corresponding physical memory values in gigabytes.
3. An alert configuration box is open, with a message indicating "High Memory Usage on Server" and a condition set to trigger when memory usage is greater than 90.
4. Options to "Edit" the alert or "Configure new alert" are available.
5. The bottom section lists operating system details of devices, including site name, device name, OS version, build number, architecture, serial number, vendor, and OS family.
6. The dashboard allows sorting and filtering for each column to customize data view.
Make.com (formerly Integromat) integration
You can now process WebHook events which Domotz generates with Make.com (formerly Integromat).
Managing Unprocessed Records in a Scenario Queue
1. In the Scenarios interface, find the "All scenarios" section under the Folders menu.
2. The main screen displays scenarios, including "Domotz Webhooks."
3. A notification appears, indicating there are unprocessed records in the queue.
4. You have two options: Click "Delete queue" to remove all records or "Process existing" to process them.
This new integration enables the processing of Domotz data in a custom way. The Domotz Public API is already an easy way to retrieve data out of Domotz with a polling mechanism, the Domotz WebHooks provide external systems with constant updates more efficiently.
However, processing WebHooks usually requires a self-hosted Web Server that receives the WebHook from Domotz and transforms the data for a target system.
With the new integration with Make.com, you get a simple system (based on Integromat) to process Domotz WebHooks for you. For instance, below are entries in a Google Sheet from events the Domotz Platform triggers (device status), which the Make.com integration then processes:
Google Sheet displaying device status logs.
1. The sheet title is "Domotz Events."
2. Column A header is "device_status."
3. Each row below the header shows a log entry detailing a device's status change:
- Row 2: Status of "PS4-9A" changed to "DOWN" on "2022-12-02" at "16:23:48".
- Row 3: Status of "PS4-9A" changed to "UP" on "2022-12-02" at "16:23:54".
- Row 4: Status of "Desk La" changed to "UP" on "2022-12-02" at "16:23:57".
4. Use these logs to track and analyze device connectivity changes over time.
For more information, please visit Make Integromat integration page.
Improvements
Additional scripts for monitoring Kubernetes
Three additional scripts are now available for monitoring Kubernetes.
- kubernetes_scheduler.js – this script can extract information about the Kubernetes scheduler (such as CPU consumption, fds open and max, memory usage, etc.).
- kubernetes_cluster_state.js – this script allows the Domotz user to retrieve status data about the Kubernetes clusters.
- kubernetes_kubelet.js – this script extracts Kubernetes kubelet metrics by HTTP agent from Prometheus metrics endpoint.
Device Details and Integration Management Interface
1. At the top, the device is labeled as "domotz_lab" with an online status and an IP address of 18.102.29.37.
2. Tabs are available for Info, Connect, Alerts, History, SNMP, and Drivers.
3. In the "Custom Integrations" section, an option to add a driver is available. A Kubernetes scheduler integration shows a status of "RUNNING" with sample period details.
4. A table lists variables such as CPU and resident memory, with corresponding values and last change details. A "Download CSV" option is available.
5. The right-side panel contains links for managing device drivers, exporting and importing device settings, and deleting the device.
6. "Latest Events" section displays details like IP changes and device status updates.
7. Options for creating connections, adding SNMP sensors, and adding TCP sensors are also provided.
For more information, please visit the Kubernetes Monitoring Integration page.
Improvements to External Host monitoring
You can now monitor External hosts/IP Addresses (see Add an external hostname/IP for more information) based on available services (e.g. WebService on port 80 or 443) rather than simply on the availability of the ICMP (Ping) service.
Some public services (or, in general, public IP addresses/hosts) do not allow to be monitored via ICMP (Ping). On the other hand, they usually offer a specific service (for instance, an http/https Web Server on port 80 or port 443, which you can use to monitor and define the status of that specific external Host/IP address. A new version of the Domotz Agent can now use this mechanism to monitor external Hosts.
For more information about this capability and how to configure a Domotz Agent to monitor an external host/IP Address based on the available service (instead of ICMP), please contact our Support (support@domotz.com).
Improved Sites Explorer view
The Sites Explorer view has gotten an update so that it is easier to identify sites with Important Devices offline, as opposed to the ones with all the Important Devices online:
Sites Explorer and Map View for Monitoring Network Issues
1. In the "Sites Explorer" panel on the left, view a list of sites, each accompanied by its status. The top shows filters such as Healthy, Issues, and Down with respective counts: 1 Healthy, 8 Issues, and 4 Down.
2. Each site listed has a status indicator with specific information, such as "Security issue found" or "Offline for 2 years." Important metrics like the number of devices online are displayed next to each site.
3. On the right, a map shows the geographical distribution of sites. Numbers on the map correspond to counts of sites in those locations, such as 7 near Los Angeles and 2 near Washington.
Moreover, it is now possible to click on either the “Offline” or “All” Important Devices number indicators, to retrieve directly only the “Offline” or the entire list of Important Devices configured for each site respectively.
Support for multiple Customers in the Syncro Integration (Asset Management)
Searching and retrieving all the customers configured in Syncro is now possible when setting up the integration between Domotz and SyncroMSP for Asset Management synchronization.
You are now able to scroll the entire list of possible customers in Syncro, as well as search for a specific one.
Custom Integration Driver list via Public API
It is now possible to retrieve the entire list of possible Custom Integration Drivers available on a specific Domotz account via Public API.
For more information, please visit List Custom Drivers section in the Domotz Public API documentation.
Select All devices when Creating Monitoring Tables (Sensors)
It is now possible to select all the devices when creating a Monitoring Table (within Monitoring Dashboard section) for sensors. This allows the user with a single click to list all the devices that have the capability of listing SNMP Sensors, rather than OS Monitoring sensors.
Additional MIBs available in the Domotz Database
Additional MIB files are available for the following devices. Additionally, you can search for their OIDs from Domotz:
- Vertiv/Liebert MIB
- Additional Synology MIB files
- HANWHA-NWC-MIB
- IMI MIB
- LifeSafety Power
Fix
We’ve fixed the following issues:
- The new vendor name for Ubiquiti (Ubiquiti Inc.) is now supported for the Unifi integration.
- Manual links with PDUs/UPS outlets disappeared in case of password (or connection) errors in retrieving data.
- On the FreshService integration, the Domotz user is now used for updating the tickets.
- NETIO Products are now correctly recognized as such.
- You can now use much longer passwords in the Custom Integration Driver configurations.
- Bonjour and UPnP data were mistakenly associated with the wrong devices.
Known limitations
- There is not a central repository for all the alerts configured on SNMP PreConfigured, OS Monitoring and Custom Integration driver sensors. We are aiming to have this available before end of Q1 2023.
- Monitoring Dashboards are currently limited to Monitoring Tables as Widgets.
- Luxul Router-based Agents do not support VPN on demand. To elaborate, we’ll add this capability as soon as Luxul’s team provides us with the required API resources.
- You can’t configure the static IP address on the Domotz Box before configuring the Agent.
- Lastly, you can’t leverage DHCP on additional VLANs on the Domotz Box.
To conclude, these release notes cover the changes in the Domotz Pro service since the previous one. Furthermore, these changes include Domotz Pro cloud, Domotz Agent, and Domotz Pro App.
Lastly, to learn more about our network monitoring software or our Know Your Networks Blog.