# June 14, 2023 – Dynamic Tables, AWS Monitoring, Ubiquiti/UniFi Controller improvements, SNMP sensors for Sophos Firewall and Dell iDRAC We have exciting new features and integrations available on Domotz. This month’s updates include dynamic Monitoring Tables, uptime statistics for all devices, more Custom Integration scripts for monitoring Microsoft Windows systems and AWS resources, pre-configured SNMP sensor templates for Sophos Firewall and Dell iDRAC, and more. **In summary, here’s what’s new on Domotz this month.** - [Dynamic list of devices in Monitoring Tables](#Dynamic-list-of-devices-in-Monitoring-Tables) - [Device Uptime Values in Monitoring Tables](#Device-uptime-values-in-monitoring) - [Support for Multiple Ubiquiti/UniFi Controllers](#Support-for-Multiple-Ubiquiti-UniFi-Controllers) - [WinRM (WMI) based Custom Scripts](#winrm-custom-script) - [Sophos Firewall Pre-Configured SNMP template](#Sophos-firewall-pre-configured-snmp-template) - [Dell iDRAC Pre-Configured SNMP template](#dell-idrac-pre-configured-snmp-template) - [Web Service Performance Monitoring](#web-service-performance-monitoring) - [iPerf Internet Speed Test Monitoring](#iperf-internet-speed-test-monitoring) - [Amazon Web Services - AWS EC2, CloudWatch, EBS, RDS, and Billing Monitoring](#amazon-web-services) We continuously improve the Domotz experience and value your feedback. If you encounter any issues or have suggestions for further enhancements, please contact our support team. ## What’s new ### Dynamic list of devices in Monitoring Tables We have a powerful new feature that enhances our monitoring tables' flexibility. With the latest update, you can create dynamic monitoring tables using custom filters. By leveraging custom filters, you can define specific criteria for including devices in your monitoring tables. A new device automatically appears in the table whenever it meets the filter conditions. This new feature is sure to save you time and effort! Managing Device Selection on a Dashboard 1. Open the "Manage Devices" window, displaying the title "Bobby MacBook Online." 2. Choose between "Static Selection" or "Dynamic Selection" for device listing. - Static Selection: Select specific devices you want to include in the table. - Dynamic Selection: Include all devices matching a custom filter, including newly discovered ones. 3. A search box labeled "Custom filters available" allows filtering of devices. 4. Listed devices include: - Cisco Switches - OS Monitored devices Online - WiFi Access Points Offline - Watchguard - All Watchguard - JB office - JB ONLINE MOBILE - Bobby's office 5. To view device information, click the "Preview of 1 device" link beside the intended device. 6. After selecting, click "Done" to apply changes. 7. Option to "Create new Custom Filter in the Inventory Dashboard" is available at the bottom. Moreover, you can create monitoring tables that adapt to changes in your network environment. For example, you can set up a table to display only your important devices currently offline across sites. Use this improvement to focus on your critical devices and take prompt action when necessary. No more manually updating your monitoring tables. Embrace the power of automation with dynamic device lists in your monitoring tables. Simplify your monitoring workflows and get real-time updates. For more information about configuring Custom Filters for your Monitoring Tables, visit our [Custom Filters](https://help.domotz.com/admin-global-features/custom-filters/) help page. ### Device Uptime Values in Monitoring Tables Our insightful new feature provides valuable uptime information for all the devices you’re monitoring. With the latest update, you can now easily track and analyze the performance of your devices right from the monitoring tables. Connectivity and Uptime Dashboard Details 1. The top section, "Connectivity Status & Uptime - CLOUD," lists cloud monitoring devices. Columns include: - **Site Name**: Location of the device. - **Device Name**: Specific name of the device. - **Type**: Shows the type of connection. - **Status**: Connectivity status duration, such as "a month" or "a day." - **RTD Worst/Median**: Round-trip delay times. - **Status Changes 24h**: Number of status changes in the last 24 hours. - **Uptime 24h/7 Days**: Percentage of uptime for the last 24 hours and seven days. - **Actions**: Options for managing devices. 2. The bottom section, "Connectivity Status & Uptime - Network Appliances," details on-premises network devices. Columns include: - **Site Name**: Location of the network appliance. - **Device Name**: Name and type of the switch, with model details. - **IP Address**: Current IP address assigned. - **Status**: Duration of current connectivity status, such as "3 years." - **RTD Worst/Median**: Highest and median round-trip delay times. - **RTD Packets Lost**: Percentage of packets lost during transmission. - **Status Changes 24h**: Counts device status changes in the past 24 hours. - **Uptime 24h/7 Days**: Device uptime percentage over the last 24 hours and seven days. Use the columns to monitor and assess device connectivity performance. For each device or service you’re monitoring, you can now access uptime statistics for the past 24 hours, 7 days, and 1 month. Moreover, this new information allows you to assess the reliability and stability of your devices over time. Uptime values in your monitoring tables also allow you to generate comprehensive reports for your end customers. You can now provide visibility into devices requiring additional attention or troubleshooting. Use this new feature to deliver a higher level of service and make informed decisions based on reliable uptime metrics. Stay on top of your network performance and gain valuable insights with device uptime values in your monitoring tables. You are also allowed to generate comprehensive reports and demonstrate the reliability of the network infrastructure to your clients and stakeholders. Using the Domotz Public API, you can also extract uptime statistics. For more information, visit[Domotz Public API - Uptime](https://portal.domotz.com/developers/#getagentlistuptime). ### Sophos Firewall Pre-Configured SNMP template We now support pre-configured SNMP sensors for Sophos Firewalls. We have new sets of pre-configured SNMP templates for Sophos firewalls: Adding Pre-configured SNMP Sensors 1. Access the "Add Pre-configured SNMP Sensors" menu. 2. Locate the section titled "Available Pre-configured SNMP Sensors." 3. Use the search bar if needed to find specific properties. 4. Review available sensors such as "Network Traffic," "Sophos Firewall General Monitoring," "Sophos Firewall Uptime," and "Sophos Firewall Policies." 5. "Network Traffic" includes details like Interface, Operational Status, and more. 6. "Sophos Firewall General Monitoring" tracks appliance key, firmware version, and memory usage. 7. "Sophos Firewall Uptime" shows uptime in milliseconds. 8. "Sophos Firewall Policies" displays policy name and connection details. 9. To select a sensor, click the checkbox next to its name. Firstly, you can use these new templates to monitor any Sophos firewall. Moreover, you can also automatically extract multiple types of information: - General Information about the status of the firewall (e.g., the Sophos Appliance Key, the Device Model, Firmware Version, Snort version, Memory and CPU usage, Number of Live Users logged into Captive Portal, and more) - The Sophos Firewall Uptime - Policy Information (e.g., configured policies, Policy Names, Connection types, Active Tunnel Counts, and more). Use our new pre-configured tables (or list of variables) to monitor your Sophos firewalls across multiple sites. Moreover, you can create  monitoring tables using this data: Sophos Firewall General Monitoring Interface 1. The table displays a list of 14 monitored firewall devices with details updated less than a minute ago. 2. Columns include "Site Name," "Device Name," "Type," "IP Address," and "Status," showing the operational state like "4 days" or "a month." 3. "SNMP Status" shows either "Read" or "Unknown." 4. "Device Model" lists models like "XG106_XN01_SFOS." 5. "Firmware Version" column shows versions like "19.5.1 MR-1-Build278." 6. "Memory Usage" and "Disk Usage" are represented by percentage bars. 7. "Live user count" and "Snort Version" provide additional device status information, with numbers and version details like "2" or "18.0.2.501." Finally, this new feature includes reporting in graph format. The reports include both historical data and statistical information. Memory Usage Graph for One Week 1. This graph shows memory usage over a one-week period from June 3, 2023, to June 10, 2023. 2. The y-axis represents memory usage percentage, ranging from 0% to 100%. 3. The x-axis displays the dates within the specified week. 4. A blue line tracks the memory usage, fluctuating around the 75% mark. 5. The top right corner offers options to zoom into different time frames: 1 day (1D), 7 days (7D), and 1 month (1M), with the 7-day view currently selected. You will find more information by visiting the [Pre-configured SNMP Sensors – Sophos Firewall](https://help.domotz.com/monitoring-management/pre-configured-snmp-sensors/#htoc-sophos-fw) help page. ### Dell iDRAC Pre-Configured SNMP template We now have pre-configured SNMP sensors available for Dell iDRAC. We have new sets of pre-configured SNMP templates for the iDRAC server: Adding Pre-configured SNMP Sensors in a Device Details Panel 1. Open the "Add Pre-configured SNMP Sensors" window. 2. In the list of available sensors, locate "Dell iDRAC General Monitoring" and "Dell iDRAC Components Monitoring." 3. For the "Dell iDRAC General Monitoring" option, details include: iDRAC Version, Dell System Service Tag, System Status, Storage Status, Power State Unit Status, and LCD Status. 4. For the "Dell iDRAC Components Monitoring" option, details include: Global System Status, Power Unit Status, Redundancy Power Unit Status, Temperature Status, Cooling Device Status, Processor Status, Memory Status, Voltage Status, Amperage Status, and Chassis Intrusion Status. 5. Select the desired sensors by checking the box next to each entry. 6. Once selections are made, proceed by clicking "Apply" to confirm changes. Firstly, you can use this new template to monitor every Dell iDRAC server. Moreover, for these servers, you can now automatically extract multiple types of information: - General Information about the status of the server (e.g., the iDRAC Version, the Dell System Service Tag, the System and Storage status, and more) - Component Monitoring (e.g., Global System Status, Power Unit Status, Temperature Status, Cooling Device Status, and more). Additionally, use our new pre-configured tables (or list of variables) to monitor your Dell iDRAC servers across multiple sites. Moreover, you can create monitoring tables using the data from this functionality. This is an example of General Information you can extract from the Dell iDRAC through this new SNMP Pre-Configured template: Dell iDRAC General Monitoring Dashboard 1. **iDRAC Version**: Displays the version details as "7.0.3 21053776 U3 P70". 2. **Dell System Service Tag**: Shows the unique identifier for the system as "2Z46WW1". 3. **System Status**: Indicates the current system status labeled as "ok". 4. **Storage Status**: Displays the status of the storage system, also labeled as "ok". 5. **Power State Unit Status**: Shows the power status, identified as "on". 6. **LCD Status**: Provides the status of the LCD, marked as "ok". Each status entry includes options for further actions. Finally, this new feature allows you to set alerts on the status of each Dell iDRAC component parameter: Configuring an Alert in Dell iDRAC Components Monitoring 1. Navigate to the Dell iDRAC Components Monitoring dashboard where various device statuses are displayed, such as Global System Status and Temperature Status. 2. Locate the alert configuration panel where you can create a new alert. 3. In the "Name" field, input the desired name for the alert, e.g., "Temperature Status Alert." 4. Set the condition for the alert by selecting "If the value is" and specify the criteria, such as "Is Different From" followed by entering "ok" in the adjacent field. 5. Choose the action "Then send an event notice to" and select a ticketing system like "Zendesk." 6. Add any additional contact channels if necessary by clicking on "add contact channels." 7. Confirm the setup by clicking "Apply" to activate the alert configuration. To find out more about [Pre-configured SNMP Sensors – Dell iDRAC](https://help.domotz.com/monitoring-management/pre-configured-snmp-sensors/#htoc-sophos-fw) visit our help section. ### Web Service Performance Monitoring We are thrilled to introduce a powerful new feature! Proactively monitor and control Web Service Performance through Domotz. With the latest update, you can easily monitor and analyze the performance of web services within your network environment. Web Services Monitoring Interface 1. Title: Web Services Monitoring - Monitor Web Services Performance. 2. Status shows as "RUNNING" in green text, indicating active monitoring. 3. Sample period is set to 5 Minutes; no variables are consumed. 4. Section: Server Response Time. 5. Table columns include "Id," "Server URL," "Response Status," and "Response Time." 6. Each row displays details for different web services, such as: - Service 1: URL "https://www.domotz.com" with a response time of 1173 ms. - Service 2: URL "https://help.domotz.com" with a response time of 1379 ms. - Service 3: URL "https://portal.domotz.com" with a response time of 344 ms. 7. All response statuses are "200," indicating successful responses. 8. A link to "Download CSV" allows exporting the data as a CSV file. The Web Service Performance script provides a comprehensive table that displays the list of monitored web services, including their URLs, response statuses, and response times.  This valuable information lets you proactively identify and troubleshoot any potential issues before they impact your IT operations. Our new scripts let you monitor your web services' health, status, and performance. Whether it's API endpoints or complete URLs, you can track the response status of each service, such as HTTP status codes. For example: - 200 for "OK, the request was fulfilled" - 404 for "Not Found" - 500 for "Internal Error" Please visit the[HTTP Response Status Codes](https://www.w3.org/Protocols/HTTP/HTRESP.html) page for more information).  Additionally, the script provides the duration for each response, giving you insights into the response time of your web services. Easily monitor the performance of your web services and take proactive measures to ensure optimal operation. By proactively identifying and addressing performance issues, you can minimize downtime. Additionally, you can optimize the user experience and maximize the efficiency of your network infrastructure. For more information about Web Services Performance Monitoring and how to utilize this powerful feature, please visit our website:[Monitor Web Service Performance](https://www.domotz.com/integrations/software/application-and-cloud-monitoring/monitor-web-services-performance.php). ### iPerf Internet Speed Test Monitoring We now support iPerf internet speed tests! You can now perform iPerf Internet Speed tests as part of your network monitoring activities on Domotz. iPerf3 is a tool for actively measuring the maximum bandwidth achievable on an IP network. With our new feature, you can quickly assess and analyze the performance of your network connections. iPerf Performance Monitoring Interface 1. The tool is identified as "iperf" with its status shown as "RUNNING" in green. 2. The sample period is indicated as "5 Minutes" and the number of variables consumed is "4". 3. There is an option to download the data in CSV format via the "Download CSV" link. 4. The "Variables" section includes a table with columns for "Name," "Value," and "Last change." 5. Under "Name," the following variables are listed: Download speed, Download speed UDP, Upload speed, and Upload speed UDP. 6. Each variable is associated with a "Value" displayed in Mb/s: Download speed at 31858 Mb/s, Download speed UDP at 1.07 Mb/s, Upload speed at 33101 Mb/s, and Upload speed UDP at 1.05 Mb/s. 7. The "Last change" column notes that each entry was updated "a few seconds ago." Our custom integration utilizes the SSH protocol to execute speed tests (iPerf3) from Linux machines. Moreover, it provides accurate measurements of download and upload speeds. Gain valuable insights into the bandwidth capacity of your network and proactively identify any performance bottlenecks or connectivity issues. The iPerf Internet Speed Test script generates comprehensive reports for each execution, including the following values: - Download speed - Download speed UDP - Upload speed - Upload speed UDP These metrics allow you to track the performance of your network connections over time. Setting up the right alerts will also notify you if there are any deviations from the speeds you expect. This feature is invaluable for troubleshooting and identifying potential bottlenecks in your network infrastructure. By incorporating iPerf Internet Speed Test monitoring into your network management workflow, you can ensure optimal network performance. Additionally, you can minimize downtime and deliver a seamless user experience. For more information on how to set up and utilize the [iPerf Internet Speed Test monitoring](https://www.domotz.com/integrations/software/application-and-cloud-monitoring/iperf-internet-speed-test.php) feature, please visit our help section. ### Amazon Web Services - AWS EC2, CloudWatch, EBS, RDS, and Billing Monitoring We have a new Amazon Web Services (AWS) monitoring integration available. Proactively monitor your AWS infrastructure and services directly through Domotz. Our AWS integration simplifies your infrastructure and application monitoring process. With our custom scripts leveraging the HTTP protocol and the CloudWatch API, you can effortlessly monitor various aspects of your AWS environment. Let's explore the different monitoring scripts available: ##### EC2 Monitoring These scripts collect essential metrics to assess the performance and health of your EC2 instances. AWS EC2 Instance Status and Variable Overview 1. The instance name is "aws_ec2" with a status of "RUNNING." 2. Sample data is collected every 5 minutes, with 17 variables consumed. 3. Key variables are listed with three columns: Name, Value, and Last change. 4. CPU utilization is at 1.4% with the last update just now. 5. Credit CPU balance is 1944, updated 30 minutes ago. 6. Network Bytes in shows 2347.0 Bps with recent changes. 7. Network Packets in is 7.21, updated just now. 8. Disk write bytes and ops are currently at 0.0 Bps and 0.0 Ops. 9. The CSV download option is available for data export. ##### CloudWatch Monitoring CloudWatch monitoring enables you to gain insights into the performance of your AWS services. AWS CloudWatch Monitoring Status and Data Table 1. The status of the AWS CloudWatch is indicated as "RUNNING." 2. The data is sampled every 5 minutes with 32 variables consumed. 3. A table displays CloudWatch metrics with columns for Id, Namespace, Dimension, and Dimension Value. 4. The table includes entries such as: - Id: "myDatabaseCPUUsage" with Namespace "AWS/RDS," Dimension "DBInstanceIdentifier," and Dimension Value "moome-1." - Id: "server1NetworkIn" with Namespace "AWS/EC2," Dimension "InstanceId," and Dimension Value "i-0f838cd543733f17f." 5. Options to filter each column using dropdown selections labeled "All." 6. A link to download the table data as a CSV file. This driver lets you retrieve CloudWatch metrics for various AWS services, including EC2, RDS, ELB, and Lambda. You can monitor many metrics, including CPU Utilization, Network In, Network Out, Disk Read Ops, Disk Write Ops, Database Connections, and many more. ##### EBS Monitoring This script provides valuable information to optimize the usage of your EBS volumes. AWS EBS Monitoring Interface Overview 1. The top-left displays the AWS Elastic Block Store (EBS) status as "RUNNING" with a sample period of "5 Minutes" and "0" variables consumed. 2. Below, a table lists various variables with three columns: Name, Value, and Last change. 3. Examples of variables include Burst balance at 100%, Idle time at 59.706 seconds, and Write bytes at 53762.090 bytes per second, with updates indicated as "a few seconds ago." 4. Use the "Download CSV" link on the right to export the table data. 5. Each column header allows sorting, enhancing data analysis capabilities. ##### RDS Monitoring These scripts provide visibility into the performance and status of your RDS instances. You can use them to monitor general information such as CPU, disk operations, network properties, storage, class, status, engine, etc. AWS RDS Monitoring Dashboard 1. The dashboard displays the status of the AWS RDS instance, which is currently running. 2. The sample period for data collection is set to 5 minutes, and a total of 16 variables have been consumed. 3. A table lists variable data, including three columns: Name, Value, and Last Change. 4. The "Burst balance" shows 100% with a recent change noted a minute ago. 5. "Credit CPU: Usage" is 0.574. 6. "Memory, freeable" is 106.20 MiB. 7. "CPU: Utilization" is displayed as 11.4%. 8. Users can download the data as a CSV file using the provided link. ##### Billing Monitoring Monitoring your AWS billing helps you keep track of your costs and prevent unexpected expenses. AWS Billing Status and Variables 1. The billing process labeled "aws_billing" is currently running, shown by the status "RUNNING" in green. 2. The sample period is set to "5 Minutes," with a total of 7 variables consumed. 3. A "Download CSV" option is available for data export. 4. The "Variables" section lists detailed billing metrics: - "AmortizedCost," "BlendedCost," "NetAmortizedCost," "NetUnblendedCost," and "UnblendedCost" each have a value of "22.199 USD." - "NormalizedUsageAmount" is listed as "759.008." - "UsageQuantity" has a value of "10144.421." 5. All variables have a "Last change" time listed as "a minute ago." All these scripts utilize the HTTP/S protocol to access AWS web services securely. To start using AWS monitoring, visit our [Amazon Web Services - AWS Monitoring](https://www.domotz.com/integrations/software/application-and-cloud-monitoring/amazon-web-services.php) page. ## Improvements ### Support for Multiple Ubiquiti/UniFi Controllers We now have a new mechanism to connect to Ubiquiti/UniFi Controllers. You can connect the same Domotz Agent directly with multiple Ubiquiti/UniFi controllers. Connecting to the Ubiquiti Unifi Controller Service 1. In the "Available External Services" section, locate the "Ubiquiti Unifi Controller" box. 2. Click the "Add Controller" option below the list of existing controllers. 3. A dialog box appears titled "Connect to the Ubiquiti Unifi Controller Service." 4. Enter the controller's hostname in the "Hostname" field (e.g., Third Controller). 5. Input the required "Username" and "Password" to authenticate. 6. Click the "Connect" button to establish the connection. In this way, if multiple controllers control Ubiquiti/UniFi devices on the same site (Domotz Site), you can extract additional information for all of them. For more information, please visit[UniFi by Ubiquiti Networks Performance Monitoring and Alerts](https://www.domotz.com/integrations/hardware/managed-network-switches-firewalls-access-points/ubiquiti-networks-unifi-performance-monitoring-alerts.php). ### WinRM (WMI) based Custom Scripts We’ve made a significant improvement to our Custom Scripts framework. We now have WinRM (Windows Remote Management) protocol support for Windows-based devices. You can execute WMI (Windows Management Instrumentation) commands within the Custom Scripts framework, providing advanced monitoring capabilities for Windows devices. Previously, all the scripts for advanced monitoring of Windows devices leveraged the SSH protocol for connecting to endpoints. With this update, we have a new set of scripts based on WinRM, enabling seamless integration with Windows devices. We have a new set of scripts that utilize WinRM as the protocol for leveraging this functionality. You can find these scripts on our GitHub repository at the following link:[GitHub Custom Driver - WinRM Examples](https://github.com/domotz/custom-driver/tree/master/examples/winrm). Additionally, we made updates to our Custom Scripts framework to support WinRM as a connection method. For detailed information on utilizing WinRM to connect to devices and execute scripts, please refer to our documentation:[Custom Driver - WinRM Options](https://portal.domotz.com/custom-driver/global.html#WinRMOptions). Take advantage of the WinRM-based Custom Scripts to enhance your monitoring capabilities for Windows devices. Monitor and easily manage your Windows-based infrastructure, leveraging the power of WMI commands. ### 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: - HP MIBs - Sharp NEC Displays - EVO MIB Tree - PaloAlto MIBs - LGE-COMMER-TVLINK-MIB - LGE-COMMER-TVLINK-WEBOS-MIB ## Fix We’ve fixed the following issues: - The History Report for String Variables was sometimes creating overflows on the screen. - The "Last Check" field on the Configuration Management capability did not correctly consider TimeZones. - The issue with the edit of the Monitoring Dashboard names. - Monitoring Dashboard was sometimes causing crashes on the Edge web browser.  - The Site Explorer list wasn’t refreshing when changing a single site status. - Dell OS Switch is not correctly identified for the Configuration Management capability. - UTF8 symbols were not accepted as names for the Monitoring Tables. - Merged devices (e.g., devices with multiple Network Interfaces) were not visible in dynamic sensor monitoring tables. - The Auto-Discovery state was affecting External Device monitoring. - Disabling Auto-discovery on Agents with the Big Network capability (monitoring up to /16 CIDR network) was not working. - An issue was causing a "configuration mixup" between devices from different sites. - Aten PDU issue preventing the user from unlocking the device capability. ## **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, learn more about our [network monitoring software](https://www.domotz.com/) or [Know Your Networks Blog](https://blog.domotz.com/).