To kick off June, here are all the latest features and improvements we’ve added to Domotz:
- We’ve added a new landing page for quick navigation as part of our interface refresh
- Network Configuration Management features are now available for MikroTik firewalls, routers, and switches
- Manual IP scan: Scan and monitor your own list of IP addresses which is very useful for those of you that do not want to scan an entire network
- Export your Network Topology Map data from our Public API
- Automatically close tickets from TCP Port status events
- New logging on Custom Integration executions
- New information for Dell iDrac and HP iLO devices
- Additional MIBs
New Landing Page and Dashboard for Quick Navigation
When you log in to Domotz you’ll land on a new “Manage” dashboard which lets you quickly navigate across multiple sites and devices. The new Manage section is the heart of your Domotz experience!
Furthermore, in this section, you’ll find your site map, be able to perform key actions, and see your dashboards as well as your KPIs. Moreover, this new dashboard allows you to quickly search across thousands of sites and hundreds of thousands of devices. Additionally, you can quickly filter a site for important devices offline, security issues, and more.
We’ve also added network setup information to your Sites including VLANs and attached networks, private subnets, and routed networks, as well as external hosts.
In the device section on Manage, we’ve added more information that allows you to quickly search for devices with specific configurations or issues. From here you can quickly access multiple functionalities and do many things such as:
- Perform direct remote connections to your preferred services
- Check and execute Round Trip Delay performance tests
- Control the power of a device
- Configure alerts on multiple devices
- Review SNMP, TCP, and other configured sensors (including Custom Drivers and OS Monitoring sensors)
- So much more!
Manual IP Scan: Scan and Monitor a list of IP Addresses you define
We’ve added a new Manual IP scan. This capability is very important when you only want to scan and monitor a subset of IP addresses on a network. You can now scan and monitor your IP addresses with ease, without affecting the rest of the network.
Configure your Domotz Agent so that it only scans for a defined list of IP addresses across a network and the networks you’ve attached to it.
To configure the Manual IP scan you must start the Domotz Agent with the discovery disabled on all interfaces (via Command-Line). For more information about how to Disable Network Scanning, please visit the following help article: Activation with Network Scanning Disabled
Once the Agent has been activated with Network Scanning disabled, you will be able to define, via our Public API the list of IP addresses that you want to scan and monitor. Learn more in the following help article: Define Agent IP Address scan Policy
The Agent will now start scanning and monitoring only the IP addresses you’ve defined within the Policy. It will not scan the rest of the network.
Network Configuration Management added for MikroTik
Our network configuration management features are now available on MikroTik (RouterOS devices) to help you stay on top of crucial changes happening in your network infrastructure.
You can now automatically backup the running configuration files of your Mikrotik devices. Additionally, Domotz will keep track of the configuration changes over time and notify you if any change occurs to help you easily identify network configuration issues.
Ticketing System Integration: TCP Events with auto-close
You can now configure the Domotz integrations with your PSA and Ticketing systems so that the software opens and automatically closes tickets based on TCP monitoring events (related to checking the status of TCP ports).
By checking the Device TCP Events box, you can configure the Domotz integration with your PSA / Ticketing system to create a new Ticket for each TCP Port it discovers as “not-available” (closed). Furthermore, Domotz will automatically close the Ticket as soon as it discovers the TCP Port is “available” (open).
Extract Network Map Topology definition from Public API
It is now possible to extract a list of nodes and connections directly from the Public API:
You can use and change the information from the API, to create your own customized Network Topology map using the tool of your choice. For example, the following is a dynamic rendering of a network’s topology using the data extracted from Domotz:
Enabled Pagination on Autotask PSA list of Accounts
When mapping Domotz Agents to your Autotask PSA account, we can now retrieve a very long list of PSA Accounts:
What’s more, is that you can now map Domotz to Autotask PSA even if there are tens of thousands of Accounts on your list. You can complete the account mapping by searching for the Account name, or by scrolling down the list across multiple pages.
Custom Integration: logging while testing drivers
We’ve added more detailed logging when running a Custom Integration against a device for development and testing purposes.
When a custom driver function is executed on a device from the Editor page, you are now able to see the following:
- the execution outcome (success or failure)
- the resulting variables (if any, in case of success)
- the execution error message reported by the Domotz Agent and the Domotz Cloud (in case of failure)
- The execution logs with the log level (Debug, Info, Warning, Error) for each log
Dell iDrac and HP iLO data
In the OS Monitoring functionality, Domotz now extracts and reports in device details additional parameters for the following two devices:
- Dell iDrac
- HP iLO
You can leverage this functionality to identify the following information:
- Physical Memory
- Physical Disks
- Logical Disks
- System CPU status (Temperature, Cache, Voltage, etc)
- System Board status (Fan, Voltage, Temperature, GPU)
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:
- NetAgent UPS modules
- Legrand/Middle Atlantic UPS
- Powersoft AV
- Draytek Vigor Router
- Voltronic/Powershield UPS
We’ve fixed the following issues:
- Firstly, the Agent was reporting unexpected DHCP servers changes, causing false-positive Alerts
- Agent was performing ONVIF broadcast discovery even if “discovery” was disabled from Domotz App/WebApp
- Agent is now capable of reading 64-bit variables through SNMP
- The issue causing the Middle Atlantic Power Cycle through Domotz overriding PDU cycle time setting has been fixed
- WAN IP Address – when the agent failed to check the WAN IP address, it removed the previous IP address discovered
- Upgraded version for Cisco Meraki API (from v0 to v1)
- Firstly, monitoring Dashboards are currently limited to Monitoring Tables as Widgets. Furthermore, they do not report some variables (e.g. the ones created by the Custom Drivers) within the Monitoring Tables.
- Firstly, 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.
- Devices with multiple network interfaces (multiple MAC addresses) can’t be merged into a single device. This affects some types of switches that appear as multiple instances on Domotz when VLANs are configured.
- The static IP address on the Domotz Box cannot be configured before configuring the Agent.
- HCP cannot be leveraged on additional VLANs on the Domotz Box.
To conclude, these release notes cover what’s changed in the Domotz Pro service since the previous Release Notes. Furthermore, these changes include Domotz Pro cloud, Domotz Agent, and Domotz Pro App.