April 23, 2024 – New Collector Settings Section, new BluOS integration scripts and additional Windows OS monitoring scripts, improvements, and more.

7 min

We’re excited to announce the newest round of updates and additions to Domotz. This April, we’re rolling out new integration scripts, like Windows OS Monitoring and BluOS, and the new Collector Settings section, providing more information on inbound and outbound bandwidth consumption, improving our network topology, improving IP-conflict resolution, and more.  

We highly value your feedback and encourage you to contact our support team at support@domotz.com for any comments, questions, or suggestions you may have.

A brand new per-device pricing model has been introduced exclusively for Partners enrolled in the Domotz Channel Partner Program (DCPP) and for select enterprise customers. 

This new per-device licensing model (rather than per-location) allows you to retain maximum flexibility in selecting which specific assets to manage via the Domotz platform while benefiting from visibility over the entire network.  Device selection is available on the new Collector Settings page (following more details).

New per-device model

To access the new pricing, partners need to contact us at sales@domotz.com to have their account enabled.

With this new section, named “Collector Settings”, you can now effortlessly configure and modify your collector(s) settings in one convenient environment.  

Currently, the Collector Settings section allows you to manage the following:   

  • Basic Information  
  • Default Credentials  
  • Documentation & Data Aggregation Platform  
  • Monitoring Configuration  
  • Booster Packs  
  • Notes

Domotz new Collector Settings section

The recent updates bring several significant improvements, enhancing your overall experience:  

  • User-Friendly Interface: The interface is even more intuitive, making navigation and settings management straightforward.
  • Centralized Management: All collector-related information can now be managed from a single access point, streamlining the process.
  • Faster Implementation: The system has been optimized for quicker setup and deployment.
  • Cost Efficiency: Last but not least, by reducing installation time, we help you save on associated costs.  

In the upcoming months, our developers’ team will work to add more management information in this section. Continue to follow us to be always updated

These new metrics provide an improved view of your network’s bandwidth usage, allowing for precise monitoring of inbound and outbound traffic through SNMP templates. You can easily analyze results, optimize network performance, identify bottlenecks, and plan for capacity.

By extending the Public API to include device SNMP status, you can leverage the Public API to automate both deployment and configuration processes.   

You can now easily verify that all devices are correctly configured with the appropriate SNMP credentials. This capability streamlines the setup process, ensuring that network devices are properly authenticated and able to communicate via SNMP. It’s a significant step forward in simplifying network management, allowing for more efficient operations and reduced manual intervention in the configuration of network devices.

This update offers customizable scan policies for external hosts, including method selection and port scanning preferences. Additionally, it enhances security and efficiency by allowing you to tailor the scan to your specific needs. More detailed guidance is available in the Domotz Public API documentation, ensuring users can maximize this feature’s potential.

VMware Virtual Machine vCenter Host Info

This script enables you to monitor the following metrics:

  • Name
  • Model
  • Operating System
  • CPU model
  • Processors
  • Cores
  • CPU usage
  • Memory
  • Memory usage
  • Power state
  • Status
  • Connection state
  • Uptime

The script has been validated and tested on VMware vCenter 8.0.2.  

VMware Virtual Machine vCenter VM Snapshots

This script allows monitoring of the following variables about the last VM snapshot:

  • Name
  • Description
  • Creation time
  • Age in days
  • ID

The script uses HTTP protocol and has been validated and tested on VMware vCenter 8.0.2.

Use the new following custom scripts to optimize your Windows OS monitoring:   

  • OS General Monitoring  
  • CPU and Memory  
  • Physical Disks  
  • Logical Disks  
  • Failed logon  

The following information can be monitored by applying the script:  

  • OS Name  
  • Version  
  • Build Number  
  • Architecture  
  • Device Serial Number  
  • Vendor  
  • OS Product ID  

This script and the following Windows-related scripts use WinRM protocol and have been validated and tested on Windows 11.  

Windows OS general Monitoring

You will have more information about the following:  

  • Total memory  
  • Available memory  
  • Memory usage  
  • CPU Name  
  • CPU max clock speed  
  • Logical processors number  
  • Cores number  
  • CPU status  
  • CPU usage  

Windows OS monitoring - cpu and memory usage

The script enables you to monitor the following:  

  • ID  
  • Model  
  • Status  
  • Size  
  • Media type  
  • Serial Number  
  • Partitions number  

Windows OS monitoring - Physical disks

Applying the Windows Logical disks script, you will be able to monitor the following:  

  • Drive letter  
  • Name  
  • Physical disk ID  
  • Usage  
  • Free space  
  • Size  
  • File System  
  • Type  
  • Is read-only  
  • Bitlocker status  
  • Bitlocker protection status  
  • Bitlocker encryption percentage  

Windows Logical Disks 1
Windows Logical Disks 2
Windows Logical Disks 3
Windows Logical Disks 4

You can monitor the following information considering the last N hours, where N can be passed as a parameter:  

  • Total number of failed logs  
  • Number of failed logons grouped by user name  
Windows OS Monitoring - Failed logon table

Take advantage of Domotz and BluOS working together to proactively monitor, control, and remotely manage BluOS amplifiers. Easily apply this script to retrieve information about BluOS devices and execute specific actions on them.  

BluOS Monitoring script

You can get access to the following information:  

  • Title 1  
  • Title 2  
  • Title 3  
  • Image – URL of the image associated with the current audio (album, station, input, etc.)  
  • Station image  
  • Stream format  
  • Stream URL  
  • Quality  
  • State  
  • Seconds – the number of seconds the current audio track has been played  
  • Volume percentage  
  • dB – volume level in dB  
  • Mute  
  • Shuffle mode  
  • Repeat mode  
  • Song – position of the current track in the play queue  
  • Can move playback – if it is possible to move the current playing or paused content to another player  
  • Can seek -if it is possible to scrub through the current track  
  • Mode  
  • Cursor  
  • Indexing  
  • Mid  
  • Status Pid  
  • Preset Id  
  • Sid  
  • Sync Stat

The following actions can be executed on a BluOS device:  

  • Change to the preset ID 1  
  • Change to the preset ID 2  
  • Change to the preset ID 3  
  • Volume up  
  • Volume down  
  • Play/pause  
  • Reboot


With improved discovery of MAC addresses through additional protocols (like SNMP, when available), this enhancement offers a more accurate and detailed network topology. It aids in identifying how devices are interconnected, especially in complex networks, enhancing visibility and control over the network structure.

This improvement combines two key network traffic monitoring possibilities into a more powerful template. It simplifies your monitoring section interface while providing a comprehensive view of network traffic, making it easier to analyze and manage network performance.

The following enhancement improves accuracy and reliability in determining an agent’s IP address. It streamlines network setup and maintenance, ensuring seamless connectivity and monitoring.

This update enhances network stability by disabling IP-conflict detection on broadcast addresses, reducing false positives and unnecessary alerts. It ensures that network administrators can focus on genuine issues, improving overall network management efficiency.   

Domotz is committed to continuously improving its IT Infrastructure monitoring and management solution for IT professionals, Managed Service Providers, and Commercial Integrators. 

In conclusion, we want to specify that Domotz will no longer support the integration scripts that run on node js 0.10.

Privacy policy

Terms and Conditions

We add support for LSI-MegaRAID-SAS-MIB. You can now monitor and manage devices using this widely used storage interface.

  • Fix the issue on the Devices Interfaces tab, not collecting traffic information with the right periodicity 
  • The “Configuration Management” tab on Device Detail was not visible until when selecting a tab  
  • The Configuration Management feature did not display a Configuration Misalignment in the ‘diff’ view  
  • Fix on Configuration Management: It cannot upload an archive backup if there are no configuration backups saved   
  • Purchasing or removing booster packs did not immediately update the limits    
  • Prevent false positive heartbeat lost events in some network edge cases (DHCPDISCOVER packets arrived while device discovery was in progress)    
  • Configuration backup for HP Aruba saves incomplete configurations in the backup file    
  • Fix the Network Troubleshooting dashboard displaying inconsistent IP Conflict data and IP Conflicts on not existing MAC Addresses    
  • New Windows Collector crashing when the SpeedTest is executed   
  • The alerts tab on Device Detail was not properly updated after importing a configuration containing an SNMP sensor trigger    
  • Manage Booster Packs when having more than 300 Collectors 
  • Fix on Configuration Management: Unlocking the Aruba OS switch results in a timeout   
  • Improve FortiGate integration timing out for some devices   
  • Fix for Contact Channels and Ticketing Systems not being displayed correctly   
  • Improve error handling for Documentation System integrations   
  • Fix IT Glue integration not accepting API key for “.com” and “.au” domains and losing mapping for Agents and Devices   
  • Fix Public API returning 503 when fetching Devices variables   
  • Fix the table detach option on the Monitoring Dashboard. The detached table was being closed when moving between Dashboards   
  • Improved percentage metrics rounding   
  • Fix link to Metrics Help Page   
  • Device Settings and Property import failed when SNMP OID triggers were selected    
  • Device Discovery via DHCP option was creating new devices from blocked interfaces; due to incompatibility reasons, Device Discovery via DHCP will be automatically turned off when one or more interfaces are blocked via Public API   
  • Improved Aruba device identification for Configuration Management    
  • Fix an issue that was preventing concurrent Scripts from running on devices 
  • Packet Loss history chart on Network Troubleshooting was not showing the chart line if all samples had 0 values    
  • Possibility to remove all emails from the IP Conflict monitoring profile    
  • Add a missing loader on the device detail SNMP view so that it is now clear if some SNMP templates are configured and are being loaded    
  • Fix the UI issue on the Monitoring Tables buttons appearing under the cell badges

Share via Social Networks

You might also like…

Read more top posts in this category

Want more tips on Network Monitoring?

Ready to get started with Domotz?

  • Powerful
  • Automated
  • Simple
  • Affordable
Start Your Free Trial Contact Sales