# August 23, 2023 – Fortinet SNMP Templates, Parametric Custom Scripts, Palo Alto SNMP Templates, Custom Filters, Standardized Serial Number

We have exciting new features, SNMP templates, and Custom scripts available on Domotz. This month’s exciting new updates include new Fortinet and Palo Alto Firewall SNMP templates, creating and editing the Custom Filters directly on the Monitoring Dashboard, parametric custom scripts, and more.

**In summary, here’s what’s new and improved on Domotz this month.**

[**New features**](#new-features)

- [Parametric Custom Scripts](#parametric-custom-scripts)
- [Fortinet FortiGate Firewall Pre-Configured SNMP templates](#fortinet-fortigate-firewall)
- [Fortinet FortiSwitch Pre-Configured SNMP templates](#fortinet-fortiswitch)
- [Palo Alto Firewall Pre-Configured SNMP templates](#palo-alto-firewall)

[**New Custom Scripts**](#new-custom-scripts)

- [Windows Latency Monitoring](#windows-audit-settings)
- [Linux Latency Monitoring](#linux-latency-monitoring)

[**Improvements**](#imrpovements)

- [Advanced Scan via TCP on Routed Subnets](#advanced-scan-via-tcp-on-routed-subnets)
- [Creating and Editing Custom Filters from Monitoring Dashboard](#create-and-edit-custom-filters-from-monitoring-dashboard)
- [Standardized Serial Number and Firmware Version](#standardized-seria-number-and-firmware-version)
- [Increase Vertical Scrollbar within the WebApp](#increase-vertical-scrollbar)
- [Enhanced "Test Script Code" Section](#enhanced-test-script-code)

[**Fix**](#fix)

We are always improving Domotz and welcome your feedback. Please contact our support team at [support@domotz.com](mailto:support@domotz.com) for help or suggestions.

## **New features on Domotz**

### **Parametric Custom Scripts**

We are thrilled to introduce a groundbreaking addition to the Custom Scripts framework within Domotz. With the newly introduced Parametric Custom Scripts, you can write custom scripts that utilize parameters that can be configured when associating the script with a specific device.

Adding a Parameter to a Script

1. In the Automation & Scripts section, navigate to the "Bulk SSL Certificate Validity" script.
2. Click "Add Parameter" under the Parameters section.
3. In the "Add Parameter" dialog box:
   - Set the "Identifier" to "certificates".
   - In the "Description" field, enter "List of domains to check for certificates".
   - For "Type", choose "List" from the dropdown menu.
4. Click "Add" to finalize and add the parameter to the script.

This innovation revolutionizes how custom scripts are employed, offering unparalleled flexibility and efficiency. With Parametric Custom Scripts, you can create dynamic and versatile scripts that cater to a wide range of scenarios. You can customize each parameter when associating the script with a device, eliminating the need for script modification or the creation of multiple script versions.

For instance, consider the SSL Certificate custom script that verifies the validity of SSL certificates. With Parametric Custom Scripts, the list of sites to be monitored can now be influenced by parameters assigned during script association.

Setting Up a Bulk SSL Certificate Validity Script

1. In the "Device Scripts Manager" window, locate and select "Bulk SSL Certificate Validity" from the list of available scripts.
2. A "Script Setup" dialog will appear. Under "Parameter," you will see a field labeled "List of domains to check for certificates Value."
3. Enter the domain name you want to check, such as "www.google.com." To add another domain, click "Add."
4. To remove a domain, click the "X" next to it, as shown with "www.domotz.com."
5. Once you have entered all the domains, click "Apply" to execute the script, or "Cancel" to exit without applying.

This empowers you to tailor your monitoring approach based on specific parameters, streamlining and enhancing your monitoring experience.

This feature enables a highly adaptable approach to network monitoring. This way allows you to monitor what truly matters to you without the hassle of modifying the script for each use case.

For comprehensive guidance on how to leverage Parametric Custom Scripts to their fullest potential, we invite you to explore the [documentation available in the Domotz platform.](https://help.domotz.com/monitoring-management/custom-driver/)

### **Fortinet FortiGate Firewall Pre-Configured SNMP templates**

We now support pre-configured SNMP templates for Fortinet FortiGate Firewalls.

Overview of Fortigate System Statistics

1. **Fortigate General/Documentation**: View serial number, firmware version, number of admin users, CPU usage, and memory usage details.

2. **Fortigate Sessions Count (IPV4 and IPV6)**: Access the ID and number of sessions for both IPv4 and IPv6.

3. **Fortigate VPN Tunnels**: Check index, username, source IP, connection IP, and traffic information including incoming and outgoing traffic.

4. **Fortigate HA Properties**: Review mode, priority, primary override status, automatic synchronization, and load-balancing configuration.

5. **Fortigate HA Stats**: Examine index, cluster serial number, CPU and memory usage, synchronization status, network bandwidth, and various rate metrics (#/s).

6. **Fortigate Hardware Sensors**: Monitor sensor values and alarm status.

7. **Fortigate WebFilter Stats**: Analyze HTTP and HTTPS session block rates, URL block rates, and cookie block rates (#/s).

8. **Fortigate Fortiguard Stats**: Evaluate HTTP/HTTPS requests examined, allowed, blocked, logged, and overridden rates (#/s).

You can use these new templates to monitor every FortiGate firewall. Moreover, you can automatically extract multiple useful information:

- General Information/Documentation
- Hardware Sensors
- FortiGuard Stats
- WebFilter Stats
- VPN Tunnels info
- IPV4 Sessions info
- IPV6 Sessions info
- High Availability Properties
- High Availability Stats

Use our new pre-configured tables (or list of variables) to monitor your Fortigate Firewalls across multiple sites. Moreover, you can create monitoring tables using the data from this functionality.

Below is an example of General Documentation that can be extracted from Fortigate using the new pre-configured SNMP templates.

Fortigate System Information Overview

1. The serial number of the device is "FG100FTK20027441."
2. The firmware version currently installed is "7.4.0."
3. There is "1" admin user configured on the system.
4. The CPU usage is at "3%," indicating low processor utilization.
5. Memory usage is at "54%," showing moderate consumption.

Each section provides key information regarding the status and configuration of the Fortigate system.

You will be able to access additional information based on the different available templates.

#### **HW (Hardware) Sensors**

- Temperature
- BCM Temperature
- CPU Temperature
- External Temperature
- Fan Temperature
- Power Supply unit condition
- Fans speed

Fortigate Hardware Sensors Overview

1. The interface displays a table with columns for Sensor, Value, and Alarm Status.
2. Under Sensor, various hardware components are listed, such as B50185 Temperature, BCM_switch Temperature, and SYS Fan1 Speed.
3. The Value column shows numerical readings, such as 66.4 for B50185 Temperature and 5469 for SYS Fan2 Speed.
4. The Alarm Status column indicates "false" for all components, meaning no alarms are active.
5. There are options to filter the list by Sensor, Value, or Alarm Status using the input boxes at the top of each column.

#### **FortiGuard Stats**

- HTTP/HTTPS requests examined
- HTTP/HTTPS requests allowed
- HTTP/HTTPS requests blocked

Fortigate Fortiguard Stats Interface Overview

1. View the section labeled "Fortigate Fortiguard Stats" to monitor statistics related to HTTP and HTTPS requests.
2. The column "HTTP request examined rate (#/s)" shows a value of 0.7108.
3. The column "HTTPS requests examined rate (#/s)" displays a value of 9.691.
4. The adjacent column, partially visible, also includes a numerical value of 0.7097.
5. Use the "Download CSV" option in the top right corner to export the data for further analysis.

Fortigate Fortiguard Stats Overview

1. The image displays statistics for Fortiguard, focusing on HTTP and HTTPS request rates.
2. The "HTTP requests allowed rate" shows a value of 0.7097 requests per second.
3. The "HTTPS requests allowed rate" displays a value of 9.517 requests per second.
4. The data can be downloaded in CSV format via a "Download CSV" link at the top-right.
5. Each section includes a filter option for refining the displayed data.

Fortigate Fortiguard Stats overview.

1. The top section displays the title "Fortigate Fortiguard Stats" with a "Download CSV" link on the right for downloading the data as a CSV file.
2. Below the title, there are columns labeled "HTTP requests blocked rate (#/s)", "HTTPS requests blocked rate (#/s)", and a partially visible "HTTP requests..." column.
3. Each column contains an input field labeled "All" indicating filtering options.
4. The first column shows the HTTP requests blocked rate as 0.001089 requests per second.
5. The second column lists the HTTPS requests blocked rate as 0.1737 requests per second.
6. The third column displays a value of 10.4, likely indicating a related metric for comparison.

#### **WebFilter stats**

- HTTP/HTTPS sessions blocked
- HTTP/HTTPS URL blocked

Fortigate WebFilter Stats Overview

1. The interface displays Fortigate WebFilter statistics.
2. Three main categories are shown: "HTTP sessions Blocked rate (#/s)", "HTTPS sessions Blocked rate (#/s)", and a partially visible "HTTP URLs Blocked rate (#/s)".
3. Each category includes a filter dropdown labeled "All" to customize the data view.
4. Below each category, numerical values represent the blocked rates: 0.0005556 for HTTP sessions, 0.06056 for HTTPS sessions, and 0.0005556 for HTTP URLs.
5. A "Download CSV" link is available at the top-right, enabling data export.

Fortigate WebFilter Stats Overview

1. The interface displays the "Fortigate WebFilter Stats" title.
2. Under "HTTP URLs Blocked rate (#/s)," see a field with the value "0.000556."
3. Under "HTTPS URLs Blocked rate (#/s)," see a field with the value "0.06056."
4. To export data, use the "Download CSV" link located at the top right.

#### **VPN Tunnels**

- Username
- Source IP
- Connection IP
- Uptime
- Incoming Traffic
- Outgoing Traffic

Fortigate VPN Tunnels Overview

1. The table displays active VPN tunnel information.
2. Columns include Index, Username, Source IP, Connection IP, and Uptime.
3. Filter options are available below each column header for narrowing results.
4. The Username column lists users associated with each VPN connection.
5. Source IP and Connection IP columns show originating and connecting IP addresses respectively.
6. Uptime indicates the duration each VPN tunnel has been active.
7. A “Download CSV” link at the top-right allows exporting the data.

Fortigate VPN Tunnels Dashboard

1. At the top, there is a "Fortigate VPN Tunnels" header indicating the section you're viewing.
2. Below the header, there's an option to download data as a CSV file, located on the right side.
3. The table displays several columns: "Connection IP," "Uptime," "Incoming Traffic," and "Outgoing Traffic."
4. Each column allows sorting and filtering by clicking the sort icon next to the column titles.
5. The data for each row includes specific connection IP addresses, the duration of uptime, the amount of incoming traffic (in MiB), and outgoing traffic (in MiB or GiB). Adjust filters as needed to view specific data.

#### **IPV4 Sessions**

Fortigate Sessions Count Table

1. The table displays the count of Fortigate sessions using IPv4.
2. There are two columns: "id" and "Number of Sessions."
3. The "id" column has a single entry with the value "1."
4. The "Number of Sessions" column shows the session count as "3577."
5. At the top-right, there is an option to download the data as a CSV file.

Graph of Session Numbers Over Time

1. This line graph displays the number of sessions from July 13 to July 14.
2. The vertical axis shows the number of sessions, ranging from 0 to 6000.
3. The horizontal axis represents time, with labels from July 13, 10:30 AM to July 14, 08:43 AM.
4. A significant drop in session numbers is observed after July 13, 01:00 PM, reaching the lowest point around midnight.
5. Session numbers start increasing again after July 14, 06:30 AM.

Zoom options for different time frames are available in the top right corner, including 1 day, 7 days, and 1 month views.

#### **IPV6 Session Count**

Fortigate Sessions Count (IPv6) Table

1. The table displays session data for Fortigate under the IPv6 category.
2. There are two main columns: "id" and "Number of Sessions."
3. Each column includes a search box, which allows filtering of data by entering specific criteria.
4. The row shows an entry with "id" as 1 and "Number of Sessions" as 5.
5. A "Download CSV" link is available at the top right for exporting the data.

#### **HA (High Availability) Properties**

- Mode
- Priority
- Status of a primary override flag
- Automatic Synchronization
- Load-balancing Configuration

Fortigate HA Properties Settings

1. **Mode** is set to "activeActive."
2. **Priority** is assigned a value of "250."
3. **Status of a primary override flag** shows "disabled."
4. **Automatic Synchronization** is "enabled."
5. **Load-balancing Configuration** is set to "roundRobin."

These settings define the High Availability (HA) configuration for Fortigate, indicating the operational mode, priority level, synchronization status, and the load-balancing method used.

#### **HA (High Availability) Stats**

- Serial Number
- CPU Usage
- Memory Usage
- Synchronization Status
- Network Bandwidth Usage
- Session Count rate
- Packets Count rate
- Bytes rate
- IDS/IPS events rate
- Anti-virus events rate

Fortigate HA Stats Dashboard

1. Device Name: Displays names such as "ClusterFortigate100E" for monitored devices.
2. IP Address: Shows IP addresses, like "192.168.X.X", for each device.
3. Serial Number: Lists the serial number of each device.
4. CPU Usage: Indicates current CPU usage percentage for each device, e.g., 4% and 0%.
5. Memory Usage: Shows memory usage percentage, such as 75% and 63%.
6. Synchronization Status: Displays the synchronization status, noted as "synchronized."
7. Network Bandwidth: Shows network bandwidth usage, e.g., 6 Mb/s and 322 Kb/s.
8. Session Count Rate: Indicates the session count rate for each device.
9. Packets Count Rate: Lists the packet count rate, such as 241.7 and 14.39.

Use the filters and sort buttons above each column to refine and organize the displayed statistics.

Fortigate HA Statistics Dashboard

1. The dashboard header reads "Fortigate HA Stats" with information stating there is one monitored device, with the last update occurring one minute ago.

2. The table contains the following columns: Device Name, Session Count rate (#/s), Packets Count rate (#/s), Bytes rate (#/s), IDS/IPS events rate (#/s), and Anti-virus events rate (#/s).

3. Below each column label, there are sorting and filtering options, allowing sorting in ascending or descending order, and filters to narrow down the data displayed.

4. Two devices, "ClusterFortigate100E", are listed under Device Name.
   - The first device shows a Packets Count rate of 145.8 and a Bytes rate of 65260.0, with all other rates at 0.0.
   - The second device shows a Session Count rate of 0.005836, a Packets Count rate of 34.35, and a Bytes rate of 28990.0, with IDS/IPS events rate at 0.0 and Anti-virus events rate as "-".

Use filters or sorting options to view specific data metrics for each device. The dash indicates non-applicable or unavailable data for certain metrics.

Finally, this new feature allows you to set alerts on the status of each FortiGate parameter you extract.

Learn more about [Fortigate Firewall Pre-Configured SNMP templates](https://help.domotz.com/monitoring-management/pre-configured-snmp-sensors/#htoc-f).

### **Fortinet FortiSwitch Pre-Configured SNMP templates**

Use the new pre-configured SNMP templates for Fortinet FortiSwitch. You can use these templates to monitor every FortiSwitch. Moreover, you can automatically extract multiple types of information:

- Serial Number
- Firmware Version
- CPU usage
- Memory usage
- Hard Disk Size
- Hard Disk Usage
- Trunk Members

Use our new pre-configured tables (or list of variables) to monitor your FortiSwitch across multiple Sites. Create monitoring tables leveraging the data retrieved using this feature.

Below is an example of General Documentation that can be extracted from FortiSwitch using the new pre-configured SNMP template:

FortiSwitch General Documentation Overview

1. Serial Number: Displays the device's serial number, beginning with "S124".
2. Firmware Version: Shows the current firmware version, FortiSwitch-124E-POE v7.2.3, build0434, 221212 (GA).
3. CPU Usage: Indicates CPU usage at 47%.
4. Total Memory: Total available memory is 233.86 MiB.
5. Memory Usage: Current memory usage is at 29%.
6. Hard Disk Size: Hard disk size is 3.00 MiB.
7. Hard Disk Usage: Hard disk usage is at 88%.

These details provide a quick status and identification for the FortiSwitch device.

Finally, this new feature allows you to set alerts on the status of each FortiSwitch parameter you extract.

Learn more about the [Pre-Configured FortiSwitch template](https://help.domotz.com/monitoring-management/pre-configured-snmp-sensors/#htoc-f11).

### **Palo Alto Firewall Pre-Configured SNMP templates**

Use these new Palo Alto pre-configured SNMP templates to monitor every Palo Alto firewall. Moreover, you can automatically extract multiple types of information:

- General Information/Documentation
- Firewall Software Versions
- Firewall Sessions
- WebFilter Stats
- Firewall High Availability Properties

Use our new pre-configured tables (or list of variables) to monitor your Palo Alto Firewalls across multiple sites. Moreover, you can create monitoring tables using the data from this functionality.

You can see an example of General Information you can extract from Palo Alto through this new SNMP Pre-configured template:

Palo Alto Firewall Identification Information

1. Serial Number: The serial number displayed is "021201053760". This unique identifier is used for tracking and support purposes.

2. Chassis Type: The chassis type is identified as "PA-440". This specifies the model of the Palo Alto Firewall being documented.

You will be able to extract additional information based on the different available templates:

#### **Software Versions**

- Hardware version
- Firmware version
- Application Definition version and release date
- Global Protect Client Package version
- Opswat Database version
- WildFire version and release date
- Antivirus version and release date
- Threat version and release date
- Wildfire Private Cloud Content version
- VPN Client Package version

Version Information for Various Components

1. Hardware version is 1.4.
2. Software version is 11.0.1.
3. Application Definition version is 8679-7870.
4. Application Definition release date is 2023/02/21 23:52:30.
5. Global Protect Client Package version is 6.1.0.
6. Opswat Database version is unknown.
7. WildFire version is 745316-748715.
8. WildFire release date is 2023/02/23 13:32:19.
9. Antivirus version is 0.
10. Antivirus release date is unknown.
11. Threat version is 8679-7870.
12. Threat release date is 2023/02/21 23:52:30.
13. WildFire Private Cloud Content version is 0.
14. VPN Client Package version is 0.0.0.

Use this information for troubleshooting or confirming current configurations of system components.

#### **Sessions**

- Maximum number of sessions
- Active Sessions
- Available Sessions
- TCP Sessions no.
- UDP Sessions no.

Palo Alto Firewall Sessions Overview

1. The "Max Sessions" field displays the maximum number of sessions, which is currently 199,998.
2. "Active Sessions" show the current number of ongoing sessions, totaling 312.
3. "Available Sessions" are those still available for use, with a current count of 199,686.
4. "TCP Sessions" display the current count of TCP protocol sessions, totaling 224.
5. "UDP Sessions" indicate the number of UDP protocol sessions, with a count of 88.

Each session type has associated trend and alert icons for further analysis or configuration.

#### **HA Properties**

- High-Availability State
- Per High-Availability State
- High-Availability Mode

Palo Alto Firewall High Availability Settings

1. The "High-Availability State" is set to "passive". This indicates the current state of the firewall in the high availability setup.
2. The "Peer High-Availability State" is set to "active". This shows the state of the peer firewall.
3. The "High-Availability Mode" is set to "active-passive". This mode determines the behavior of the primary and secondary devices in the setup. Use this configuration to ensure failover capability, where one firewall is active and the other is on standby.

Finally, this new feature allows you to set alerts on the status of each Palo Alto Firewalls parameter you extract.

Learn more about [Pre-Configured Palo Alto Firewall templates](https://help.domotz.com/monitoring-management/pre-configured-snmp-sensors/#htoc-p).

## **New Custom Scripts**

You can use the custom scripts to monitor and manage network-connected devices, cloud services, and web applications. By using standard network protocols, these scripts will allow you to retrieve valuable data and execute actions on the monitored devices and services.

This month we released the following:

- [Windows Latency Monitoring](#windows-audit-settings)
- [Linux Latency Monitoring](#linux-latency-monitoring)

### **Windows Latency Monitoring**

You can now monitor the Microsoft Windows host's latency from end-point to end-point by applying our ready-to-use, pre-configured script.

The script uses the ping command to retrieve detailed information about latency from one host to another, and you can specify a list of hosts.

The script has been validated and tested on Windows 10, Windows 11, and Windows Server 2019.

You can find these scripts in [our library](https://portal.domotz.com/webapp/#/integrations?tab=scripted_integrations). Simply personalize the drivers according to your requirements.

Following, you can see examples of the data you can extract through this specific custom script:

Network Monitoring Dashboard Overview

1. The server "DC01" is shown as online, with an IP address of 192.168.0.63 and a connection duration of 15 minutes and 50 seconds.
2. The monitoring status is displayed as "RUNNING" with a sample period of 5 minutes, consuming 15 variables.
3. The "IP Latency" section lists several entries showing ID, IP Address, Latency, and Packet Loss.
4. Specific IP addresses such as 192.168.0.1 and 8.8.8.8 have corresponding latencies ranging from 3 ms to 171 ms, with 0% packet loss.
5. A "Download CSV" option is available for exporting the data.

IP Latency Monitoring Dashboard

1. The dashboard title is "windows_monitorIPLatency" with the current status marked as "RUNNING."
2. The sample period is set to "5 Minutes" and 9 variables are consumed.
3. Under the "IP Latency" section, there is a table with four columns: Id, IP Address, Latency, and Packet Loss.
4. The first row displays an Id of "26f73d1217ffaf1846a4..." with IP Address "8.8.8.33," Latency of "-1 ms," and Packet Loss of "100%."
5. The second row shows an Id of "838c4c257384f58e74..." with IP Address "8.8.8.8," Latency of "9 ms," and Packet Loss of "0%."
6. The third row includes an Id of "842b949c6959da939d1..." with IP Address "8.8.4.4," Latency of "9 ms," and Packet Loss of "0%."
7. Use the "Download CSV" link to export the data.

### **Linux Latency Monitoring**

Monitor a Linux host's latency from end-point to end-point by applying our ready-to-use, pre-configured script.

The script uses the ping command to retrieve detailed information about latency from one host to another, and users can specify a  list of hosts. It has been validated and tested on Ubuntu 20.04 LTS.

You can find these scripts in [our library](https://portal.domotz.com/webapp/#/integrations?tab=scripted_integrations). Simply personalize the drivers according to your requirements.

Following, you can see examples of the data you can extract through this specific custom script:

Network Monitoring Dashboard Overview

1. The dashboard title is "domotz_lab" with the status showing as "online" with an IP address displayed. User information includes "@mariem" and status as "Unknown."

2. The section labeled "linux_iplatency" displays a "RUNNING" status. The sample period is set to "5 Minutes," and no variables are consumed.

3. The "IP Latency" table provides details including columns for Id, IP Address, Latency, and Packet Loss. Each column includes filtering options.

4. IP addresses listed are "10.41.131.10," "8.8.8.8," and "1.1.1.1," with corresponding latency times and packet loss percentages. All packet loss values are at 0%.

5. A link is available to download the data in CSV format.

IP Latency Monitoring Dashboard Overview

1. The dashboard is titled "linux_monitorIPLatency" and indicates the monitoring status as "RUNNING."
2. Displays a sample period of "5 Minutes" and shows "Variables consumed: 0."
3. There are options to download the data as a CSV file.
4. The table lists IP latency details with columns for Id, IP Address, Latency, and Packet Loss.
   - The first row shows an IP Address of 8.8.8.33 with a latency of -1 ms and 100% packet loss.
   - The second row lists 8.8.8.8 with 0.662 ms latency and 0% packet loss.
   - The third row features 8.8.4.4 with a latency of 0.454 ms and 0% packet loss.

## **Improvements** **on Domotz**

### **Advanced Scan via TCP on Routed Subnets**

Domotz's network scanning capabilities have become more powerful. You can now configure scans on Routed Subnets using the TCP port monitoring mechanism instead of the ICMP mechanism.

Creating a Routed Network in a Software Interface

1. Go to "Configured Routed Networks" and click on "Add a Routed Network."
2. In the "Create a Routed Network" dialog, enter the IP address of your subnet in the "Name" field.
3. Enter the subnet mask, for example, "255.255.255.0," in the "Subnet Mask" field.
4. Optionally, check "Advanced Scan via TCP" to enable this feature.
5. Click "Proceed" to save the configuration or "Cancel" to exit without saving.

The Advanced Scan via TCP offers a robust alternative if devices cannot be effectively identified and monitored via simple ping (ICMP mechanism). This feature provides the flexibility to monitor devices on Routed Subnets with greater accuracy and reliability.

With Advanced Scan via TCP, you can ensure comprehensive visibility into your network environment, even for devices that are not responsive to ICMP-based scans. This improvement aligns with our commitment to offering adaptable and effective solutions for your network monitoring needs.

For detailed information on configuring Routed Network Scans using the Advanced Scan via TCP feature, we encourage you to refer to the comprehensive guide available at [How to Configure Routed Network Scan](https://help.domotz.com/monitoring-management/routed-network/).

### **Creating and Editing Custom Filters from Monitoring Dashboard**

We have expanded the capability to create and edit Custom Filters directly from the Monitoring Dashboard interface.

This improvement streamlines the process of creating monitoring tables that involve dynamic lists of devices and entities. When configuring a Monitoring Table and selecting a dynamic list of devices and entities, you can now access the editing section of Custom Filters right from the Monitoring Dashboard area.

Managing Device Connectivity Status and Uptime

1. In the "Manage Devices" window, you can choose to select devices by "Static Selection" or "Dynamic Selection." "Static Selection" involves manually selecting devices, while "Dynamic Selection" automatically includes devices matching a custom filter.
2. A list of available custom filters is displayed. You can choose one to apply to your device list.
3. To edit an existing filter, select the "Edit" option next to the desired filter.
4. To create a new custom filter, click on the "Create a new Custom Filter" link at the bottom of the list.
5. Buttons at the bottom allow you to navigate back or proceed to the next step.

With this enhancement, you no longer need to navigate away from the Monitoring Dashboard to create or modify custom filter rules. This seamless integration ensures a smoother process for creating monitoring tables based on dynamic selections of devices and entities.

### **Standardized Serial Number and Firmware Version**

We are excited to introduce a significant enhancement to how Domotz extracts and reports critical device information. With this improvement, Domotz consistently standardizes the extraction and reporting of each device's serial number and firmware version.

Whether extracted through SNMP, UPnP, Bonjour, WMI, Custom Script functionality, or other protocols, these critical details are now presented under each device's System section of the Info tab. In this way, you can easily access and identify these essential pieces of information.

Network Status and System Information Interface

1. The interface displays a locked icon indicating that all services are unlocked.
2. Navigation tabs include Info, Connect, Alerts, History, SNMP, TCP, Outlets, and Scripts.
3. The Status section shows "ONLINE" with the last status change occurring 4 days ago.
4. Status Changes in the past 24 hours are listed as 0.
5. The Latest Ping Round-Trip Delay (RTD) is shown as 2 milliseconds.
6. Packet Loss and Historical Ping Range are displayed, with a range between less than 1ms to 12ms.
7. The System section shows the Firmware version as 3.002.0039, dated Tue Nov 29 12:59:28 EST 2022.
8. The Serial Number is partially obscured for privacy.

The standardization of serial numbers has other benefits. The firmware version will be vital in synchronizing with Documentation systems and Asset Management platforms like, for instance, IT Glue. Additionally, these standardized details will be reflected in the Domotz Inventory Dashboard.

This improvement streamlines your network documentation processes and enhances overall asset management. You can confidently rely on accurate, standardized information when collaborating with documentation systems and asset management platforms.

### **Enhanced "Test Script Code" Section**

We are excited to share a significant enhancement to the Domotz IDE experience for testing Custom Scripts. The execution result window when testing a custom script in the Domotz IDE has undergone substantial improvements aimed at simplifying the process of debugging scripts.

With this enhancement, the execution result window now provides a clearer and more informative experience for script debugging. Introducing new types of information, warning, and error messages in the Execution Result enhances your ability to identify and understand errors or unexpected behaviors in your scripts.

This improved visibility streamlines the debugging process, making pinpointing specific issues and taking corrective actions easier.

Execution result for SSL certificate validity check.

1. The window displays the results of a script checking SSL certificate validity. It lists three entries with details.

2. Each entry shows information under the headings: "Id," "Issuer," "Expiry," "Remaining days," "Is valid," and "Auth error."

3. The first entry is for "portal.domotz.co" issued by "Sectigo Limited," expiring on Jul 17, 2024, with 333 days remaining. Valid status is "True" with no authentication error.

4. The second entry is for "domotz.com" issued by "Let's Encrypt," expiring on Nov 15, 2023, with 87 days remaining. Valid status is "False" due to a "CERT_HAS_EXPIRED" error.

5. The third entry is for "google.com" issued by "Google Trust Services," expiring on Oct 23, 2023, with 64 days remaining. Valid status is "True" with no authentication error.

6. Below the table, a console log includes details such as script execution creation and multiple "Performing GET towards" actions.

7. A red error message states, "Error: Exceeded maxRedirects. Probably stuck in a redirect loop https://twitter.com:443/."

8. The script appears to be extracting information about SSL certificate validity and logging the process, including any errors encountered.

9. A "Close" button at the bottom indicates the option to close the results window.

As a next step, we will continue refining this area to provide you with a seamless and intuitive platform for writing custom scripts. This ongoing effort aims to empower you to create and fine-tune custom scripts more easily and efficiently.

Stay tuned for more updates as we work diligently to make writing custom scripts an even more user-friendly and productive experience.

As always, we value your feedback and are here to assist you. If you have any questions or require support, please don't hesitate to contact our team.

### **Increase Vertical Scrollbar within the WebApp**

We have increased the width of the Vertical Scrollbar within the WebApp interface, enhancing usability for users who do not have a touchpad or a mouse with a scrolling wheel.

With this improvement, navigating through pages within the WebApp becomes more convenient, as the wider scrollbar makes it easier to grasp and scroll up and down. This improvement ensures a seamless user experience regardless of the input device being used.

We continuously enhance the usability of the Domotz WebApp. Your feedback is valuable in driving these improvements. If you have any suggestions or encounter any issues, please don't hesitate to contact our support team.

## **Fix**

We’ve fixed the following issues:

- Missing label on DHCP Variables.
- Searching for variables with the character "_" in the name was impossible.
- Sorting tables in the Monitoring Dashboard when opening a new window was causing sporadic crashes in the App.
- Uptime stats for 30 days time-window wrongly reported 0% in some circumstances.
- Netgear Switch M4300-12X12F was wrongly identified as an HTTP PoE version.
- Cisco Sx220 PoE switch integration did not require credentials after identification.
- Attempting to delete 2 Drivers subsequently crashes the WebApp.
- Halo PSA general ticket default did not match the Domotz ticket type.
- The Domotz Agent retrieved incorrect values for Serial Numbers through the Bonjour protocol.
- Script execution with AUTHENTICATION_ERROR incorrectly stored credentials when sending credentials.store = true.
- A Custom Script with the wrong variable type could crash the backend component.
- Dell iDRAC issue unlocking the device.
- Fixed an issue that prevented the deletion of the Unifi Cloud Controller.

## **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.

These release notes cover the changes, including Domotz Pro Cloud, Domotz Agent, and Domotz Pro App. Learn more about our software on our[website](https://www.domotz.com/) or read our[blog](https://blog.domotz.com/) to stay updated with modern network and IT Infrastructure monitoring and management.