Domotz allows you to monitor TCP Services and SNMP (v1, v2, v3) objects available on your connected devices. We conventionally call these entities as Domotz Eyes. In this article we describe:
- How to configure and monitor TCP Services
- How to configure and monitor SNMP objects
- How to tune the usage and the sampling interval of Domotz Eyes
- Other usage of SNMP within Domotz
Monitoring TCP Services
In order to monitor TCP services exposed by a device, go to the Eyes tab within the Device screen.
You can add a service to be monitored by clicking on Add a TCP Service and entering the name of the service or TCP port number associated.
Once the TCP service is added, the Domotz Agent will start monitoring that service. The port will be marked as available (green) if the Service is available on that port or unavailable (red) if not:
On every single TCP service monitored, the user can set a “Custom” alert (from the Alerts tab) to be informed when the service change status (from available to unavailable and vice-versa):
Monitoring SNMP objects
Domotz allows you to monitor SNMP OIDs explicitely, by polling periodically the device and displaying the extracted value. In particular:
- Domotz provides featuers to facilitate the MIB navigation and identify the right OIDs.
- Numerical values are also put in charts.
- You can configure alerts, based on conditions on the extracted values.
- It is possible to change the polling frequency.
- SNMP versions v1, v2 and v3 are supported.
Enabling SNMP Monitoring on a device
First of all, make sure that SNMP is enabled on the device you want to monitor.
Next step is to tell Domotz the related credentials. This can be done from the Device Access Manager, in the upper part of the Device Details screen.
Domotz will prompt a dialog for inserting the protocol credentials:
Configuring SNMP sensors
In the Device Details screen go to the Eye tab and click on ‘Add an SNMP Sensor‘.
The following dialog will appear. If Domotz already knows the MIB corresponding to the device a navigation panel will allow you to select the right OID to monitor.
If Domotz does not have any associated MIB, you can still configure OIDs manually by clicking on Manually define an SNMP Sensor, by entering the OID you want to monitor and assigning a name, description and a type to it.
Domotz will confirm that the OID is in the correct format but cannot check that the value entered is valid.
The type of value the OID will return must match the manufacturer documentation and is important for the types of Alerts you wish to create.
Monitoring SNMP sensors
Once you have configured your sensors you will see them listed in the Eyes section with the value that the device is returning for that OID, and the last time the information has been updated.
Domotz also keeps the history of numerical OIDS. By clicking on the chart icon you will see a chart like the following:
Alerts on SNMP sensors
You can configure alerts on the SNMP sensors you have created from the Alerts section of the device:
Domotz will ask you to choose one among the sensors you have already created (it will also prompt here in case wont to to create a new one):
After chosen a sensor, you will be finally able to configure the alert, by assigning a Name, a Condition, and the Communication Channel for the alert:
And, finally, the alert is configured:
Domotz Eyes: usage and sampling configuration
All Eyes (TCP services and SNMP sensors) configured within Domotz are listed in a specific section, that is accessible from the right side of menu of the Device List of an agent:
This page will give an overview of all the eyes configured and will allow you to change the sampling frequency of the Domotz Eyes (increasing the frequency will decrease the number of Eyes you can monitor):
Other usage of SNMP within Domotz
SNMP is a powerful protocol. It is also used by Domotz to implement Network mapping algorithms, PoE management as well as Network Interface Monitoring. Please refer to the respective sections for more details.
Important to remark that these features are only available if Domotz knows the SNMP credential of devices.
Please make sure that these are configured through the Access Manager of devices: