5 min
We’ve just released exciting features on Domotz. Add more than one Booster Pack to the same Agent, Sony AVR Support, additional Custom Integration scripts for better monitoring Microsoft Windows systems, pre-configured sensor templates for WatchGuard Firewall SNMP monitoring, and more.
In summary, here’s what’s new on Domotz this month.
What’s new
Cumulative Booster Packs
With this new feature, you can add more than one Booster Pack to the same Agent/Site. Adding a booster pack extends the capabilities of each agent.
Moreover, you can monitor more devices across additional routed subnets or external IP addresses. Additionally, you can perform more API calls, add more SNMP or Custom Integration Sensors, and expand the traffic on remote connections. By allowing the cumulative use of Booster Packs, you’ll gain even more insights into your networks and systems. Furthermore, this helps you better manage and optimize your infrastructure.
Currently, the maximum number of Booster Packs that can be added to a single Domotz Agent / Site is 5. However, if you need to add more, contact Domotz Support to inquire about building a custom plan. Contact us to extend further the capabilities of a single Domotz Agent / Site.
Windows: Monitor Windows Active Directory Privileged Users
Our new custom integration script enables you to proactively monitor Windows Active Directory Privileged Users and Groups with Domotz.
.
“Privileged” accounts and groups in Active Directory are those to which powerful rights, privileges, and permissions.
Proactively monitor “Privileged” accounts and groups in Active Directory with Domotz.
- Monitor the total number of privileged users in Active Directory
- Easily monitor Windows Active Directory privileged users count:
- Monitor the number of privileged users in Active Directory divided by group membership
Learn more about Monitoring Windows Active Directory Privileged Users by visiting the official documentation.
Windows: Monitor Windows Security Events
We now have a custom integration script for Windows Security Event Monitoring. This new script allows you to monitor the following Windows Security Events:
By leveraging PowerShell commands, you can use our brand-new script to monitor the following Windows Security events:
- 4720: A user account was created
- 4722: A user account was enabled
- 4731: A security-enabled local group was created
- 4732: A member was added to a security-enabled local group
- 4649: A replay attack was detected
- 4741: A computer account was created
- 4625: An account failed to log on
- 4817: Audit settings on objects were changed
- 4947: A change has been made to Windows Firewall exception list. A rule was modified
- 4948: A change has been made to Windows Firewall exception list. A rule was deleted
Learn more about Windows Security Event monitoring by visiting the official documentation.
Windows: Monitor Windows Endpoints to check reachable hosts
We have a new custom integration script for Monitoring Windows Endpoints for reachable hosts. Our custom integration script to Monitor Windows Endpoints allows you to monitor if hosts are reachable, get notified of value changes, monitor whether a VPN connection is up and running, and so much more.
An everyday use case for this is monitoring whether a VPN connection established directly from a Windows endpoint is up and running.
Review the official documentation to learn more about Monitoring Windows Endpoints for Reachable Hosts.
Windows: Monitor Windows CPU usage
We have another new Custom integration script that enables you to proactively monitor Windows CPU usage with Domotz.
Know the processing power exhaustion for processing data and running programs on your Windows Machines.
Proactively Monitor and get Alerts on Windows CPU usage using Domotz.
Learn more about Monitoring Windows CPU Usage by visiting the official documentation.
Windows: Monitor Windows Group Policies (GPOs) versions
We also have a new Custom integration Script for Monitoring Windows Group Policies (GPOs), including versions. With this new script, you can monitor:
– AD Version (User)
– SYSVOL Version (User)
– AD Version (Computer)
– SYSVOL Version (Computer)
Learn more about Windows Group Policy Monitoring by visiting the official documentation.
Improvements
Sony AVR Support
We’ve added capabilities to support Sony devices within our Sony Device integration. In particular we have added the capability terminate running apps on Sony TV Screens.
Possibility to configure an alert “on change” event
You can now configure alerts that are triggered when the value of a variable changes. This improvement is available for Pre-Configured SNMP, OS Monitoring, and Custom Integrations variables.
With this feature, you can quickly identify changes in your network or system and take proactive steps to address any issues.
Pre-configured WatchGuard Firewall SNMP sensor templates
We now have WatchGuard Firewall SNMP sensors which are pre-configured. We’ve added new sets of pre-configured SNMP templates for WatchGuard firewalls:
Firstly, you can use this new template to monitor every WatchGuard firewall. Moreover, for these firewalls, you can now automatically extract multiple types of information:
- General Information about the status of the Firewall (e.g., the Software Version, the CPU Utilization, Memory available, Current Active Connection
- Cluster Information (e.g., Cluster Status, First Member Role, and Health, Second Member Role and Health)
- Policies Information (e.g., configured policies, Discarded Packets Rate, Logging configuration, Active Connections per Policy, Tunnel Rates, and Traffic).
You can use each new pre-configured table to create a new Table (or list of variables) to monitor your WatchGuard firewalls better. You can add the data retrieved through this functionality to the Monitoring Tables:
Finally, this new feature includes reporting in graph format. The reports include both historical data and statistical information.
For more information, visit Pre-configured SNMP Sensors – WatchGuard Firewall.
HaloPSA Integration – possibility to select Ticket Type
You can choose the Ticket Type when setting up the HaloPSA integration for Ticketing Systems. Choose the ticket type to use when creating tickets in HaloPSA:
Moreover, you can define a specific custom type to identify the tickets created through the Domotz integration. This provides you with greater flexibility and organization when managing tickets in HaloPSA.
Added Organization, Contract ID, and Customer ID information in Public API for Agents
There is new information available via the Public API for your Agents. You can now access the Organization information, Contract ID, and Customer ID in the API to list all the agents or view data for a specific agent. This enhancement will make it easier for you to retrieve critical information. Additionally, it improves how you manage agents.
Visit https://portal.domotz.com/developers/#listagents and https://portal.domotz.com/developers/#getagent to access the updated API.
Please note that while this information is accessible through the API, the configuration of the Organizations, as well as specifying Contract ID or Customer ID connected to the specific Domotz Agent / Site, is still restricted to the Domotz UI (App or WebApp).
Fix
We’ve fixed the following issues:
- Fixed several warnings/errors introduced in the Domotz WebApp (in the Browser Console).
- Fixed an issue causing the Team Member (configured as Impersonator of the Admin account) not to see any Domotz Agent.
- Custom Integration Scripts using the “WinRM” protocol wrongly displayed HTTP as a credential protocol.
- FreshDesk integration: mandatory “Fields” were missing from the UI.
- Inventory Dashboard: the list of Agents/Sites belonging to a specific Organization was broken in case of inactive Agents attached to that specific Organization.
- IT Glue Integration: the “Select All” devices filter has been fixed.
- OS Management unlocking has been fixed.
- Public API: the listAgentDeviceVariables also returned the previously “Deleted” devices (for which the variables/history was still available).
- OS Monitoring capability was failing in unlocking the iDrac service.
- Fixed an issue in the response format for the Configuration Management functionality.
- Fixed an issue preventing the execution of WAN TCP Port scan on a specific set of Domotz Agents.
- The monthly report did not report some of the latest capabilities introduced in Domotz among the list of Activities (e.g., Custom Integration Actions, Sony AVR commands, etc.).
Known limitations
- There is no central repository for all the alerts configured on SNMP PreConfigured, OS Monitoring, and Custom Integration script sensors.
- 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.
- 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.