v.218 Release Notes
Last updated on 04 March, 2025Account Information
Legacy UI for Ops Notes Deprecation
As LogicMonitor continues to phase out the legacy UI, the New UI Preview switch will be removed for the global Ops Notes settings available in the Settings page, making these Ops Notes settings unavailable using the legacy UI, and available in the new UI only. The new UI provides an enhanced user experience, improved performance, and security features.
Recommendation: To prevent disruption to your workflows, navigate to Settings > Ops Notes, and then toggle on the New UI Preview switch to familiarize yourself with the new UI and take advantage of the latest features and enhancements.
For more information about this deprecation, including timeline and further updates about the removal, see Notice for Upcoming Deprecation of Websites, Reports, and Settings pages from Legacy UI in LM Community.
For the most up-to-date information about Ops Notes, see Ops Notes in the product documentation.
Note: This deprecation does not impact the availability of earlier versions of the Dashboards or Resources pages, including the ability to add Ops Notes in the legacy UI from the Resources page.
If you have any questions or require assistance during this process, contact the Support team or your Customer Success Manager.
Legacy UI for Account Information Deprecation
As LogicMonitor continues to phase out the legacy UI, the New UI Preview switch will be removed for the following in Account Information:
- Portal Information
- Portal Settings
- Financial
This removal makes Account Information unavailable in the legacy UI, and available in the new UI only. The new UI provides an enhanced user experience, improved performance, and security features.
Recommendation: To prevent disruption to your workflows and to familiarize yourself with the new UI and take advantage of the latest features and enhancements, navigate to Settings > Account Information, and then toggle on the New UI Preview switch.
For more information about this deprecation, including timeline and further updates about the removal, see Notice for Upcoming Deprecation of Websites, Reports, and Settings pages from Legacy UI in LM Community.
For the most up-to-date information about Account Information, see the following in the product documentation:
Note: This deprecation does not impact the availability of earlier versions of the Dashboards or Resources pages, including the ability to add Ops Notes in the legacy UI from the Resources page.
If you have any questions or require assistance during this process, contact the Support team or your Customer Success Manager.
Legacy UI for Audit Logs Deprecation
As LogicMonitor continues to phase out the legacy UI, the New UI Preview switch will be removed for Audit Logs, making Audit Logs unavailable using the legacy UI, and available in the new UI only. The new UI provides an enhanced user experience, improved performance, and security features.
Recommendation: To prevent disruption to your workflows, navigate to Settings > Audit Logs, and then toggle on the New UI Preview switch to familiarize yourself with the new UI and take advantage of the latest features and enhancements.
For more information about this deprecation, including timeline and further updates about the removal, see Notice for Upcoming Deprecation of Websites, Reports, and Settings pages from Legacy UI in LM Community.
For the most up-to-date information about Audit Logs, see Audit Logs in the product documentation.
Note: This deprecation does not impact the availability of earlier versions of the Dashboards or Resources pages.
If you have any questions or require assistance during this process, contact the Support team or your Customer Success Manager.
Alerts
Legacy UI for Alert Message Templates Deprecation
As LogicMonitor continues to phase out the legacy UI, the New UI Preview switch will be removed for the Alert Message Templates, making the templates unavailable using the legacy UI, and available in the new UI only. The new UI provides an enhanced user experience, improved performance, and security features.
Recommendation: To prevent disruption to your workflows, navigate to Settings > Message Templates > Alert Messages, and then toggle on the New UI Preview switch to familiarize yourself with the new UI and take advantage of the latest features and enhancements.
For more information about this deprecation, including timeline and further updates about the removal, see Notice for Upcoming Deprecation of Websites, Reports, and Settings pages from Legacy UI in LM Community.
For the most up-to-date information about the Alert Message Templates, see Managing Alert Messages Template in the product documentation.
Note: This deprecation does not impact the availability of earlier versions of the Dashboards or Resources pages.
If you have any questions or require assistance during this process, contact the Support team or your Customer Success Manager.
Legacy UI for Alert Settings Deprecation
As LogicMonitor continues to phase out the legacy UI, the New UI Preview switch will be removed for the Alert Settings, making the settings unavailable using the legacy UI, and available in the new UI only. The new UI provides an enhanced user experience, improved performance, and security features.
Recommendation: To prevent disruption to your workflows, navigate to Settings > Alert, and then toggle on the New UI Preview switch to familiarize yourself with the new UI and take advantage of the latest features and enhancements.
For more information about this deprecation, including timeline and further updates about the removal, see Notice for Upcoming Deprecation of Websites, Reports, and Settings pages from Legacy UI in LM Community.
For the most up-to-date information about Alert Settings, see Alert Delivery Overview in the product documentation.
Note: This deprecation does not impact the availability of earlier versions of the Dashboards or Resources pages.
If you have any questions or require assistance during this process, contact the Support team or your Customer Success Manager.
Cloud Monitoring
Enhanced Support for Amazon EKS and Q Business
LogicMonitor now supports expanded Elastic Kubernetes Service (EKS) monitoring, as well as Amazon Q Business.
EKS now monitors clusters through CloudWatch API, in addition to previous support for EKS container monitoring through Argus.
For more information, see Cloud Services and Resource Units in the product documentation.
Collector Settings
Legacy UI for Collector Settings Deprecation
As LogicMonitor continues to phase out the legacy UI, the New UI Preview switch will be removed for the Collector Settings, making the settings unavailable using the legacy UI, and available in the new UI only. The new UI provides an enhanced user experience, improved performance, and security features.
Recommendation: To prevent disruption to your workflows, navigate to Settings > Collectors, and then toggle on the New UI Preview switch to familiarize yourself with the new UI and take advantage of the latest features and enhancements.
For more information about this deprecation, including timeline and further updates about the removal, see Notice for Upcoming Deprecation of Websites, Reports, and Settings pages from Legacy UI in LM Community.
For the most up-to-date information about the Collector Settings, see About the LogicMonitor Collector in the product documentation.
Note: This deprecation does not impact the availability of earlier versions of the Dashboards or Resources pages.
If you have any questions or require assistance during this process, contact the Support team or your Customer Success Manager.
Cost Optimization
Enhanced Recommendation Savings using Local Collectors
Configuring a local Collector in your AWS environment now captures EC2 memory utilization.
This improves savings potential from Cost Optimization Recommendations when detecting underutilized EC2 instances, and lowers risk of negative app performance from recommended configurations.
For more information, see Cost Optimization – Recommendations in the product documentation.
Dashboards
Enhanced Dashboard Filtering with Instance Property Filters
Instance Property Filters allow you to filter dashboards based on specific instance properties, providing deeper insights into your data.
To use this feature, navigate to Dashboards > Filters > Instance Property Filters.
Note: You must first apply resource property filters to enable instance property filters.
In addition, Instance Property Filters are available only for the following widgets:
- CustomGraph
- PieChart (excluding Resource Count)
- Gauge
- BigNumber (excluding Resource Count)
- Custom Table
- Dynamic Table
For more information, see Creating Dynamic Filters in our product documentation.
Integrations
Customizable Alert Notification Title for Slack Integration
You can now customize the title of the alert notification in Slack integration. You can use plain text and tokens to customize the notification title as per your need, similar to how the message body (Alert Data) is configured. This enhances the user experience, particularly for mobile device users, by providing immediate and relevant context without the need to open the full message.
Note: While customizing the alert notification title, you must adhere to the character display limits of mobile notifications.
Customizable Alert Notification Title for MS Teams Integration
You can now customize the title of the alert notification in MS Teams integration. You can use plain text and tokens to customize the notification title as per your need, similar to how the message body (Alert Data) is configured. This enhances the user experience, particularly for mobile device users, by providing immediate and relevant context without the need to open the full message.
Note: While customizing the alert notification title, you must adhere to the character display limits of mobile notifications.
Legacy UI for LM Integrations Deprecation
As LogicMonitor continues to phase out the legacy UI, the New UI Preview switch will be removed for the out-of-the-box (OOTB) LM Integrations, making the integrations unavailable using the legacy UI, and available in the new UI only. The new UI provides an enhanced user experience, improved performance, and security features.
Recommendation: To prevent disruption to your workflows and to familiarize yourself with the new UI and take advantage of the latest features and enhancements, navigate to Settings > Integrations, and then toggle on the New UI Preview switch. You can navigate to and configure settings for each OOTB Integration.
For more information about this deprecation, including timeline and further updates about the removal, see Notice for Upcoming Deprecation of Websites, Reports, and Settings pages from Legacy UI in LM Community.
For the most up-to-date information about LM Integrations, see LogicMonitor Integrations Overview in the product documentation.
Note: This deprecation does not impact the availability of earlier versions of the Dashboards or Resources pages.
If you have any questions or require assistance during this process, contact the Support team or your Customer Success Manager.
Modules
NVIDIA SMI Monitoring
LogicMonitor now provides support for monitoring NVIDIA GPUs. LogicMonitor’s Nvidia-SMI monitoring is optimized for fast efficient parsing, enabling scaleability to larger setups on a single collector with minimal impact to overall collector performance. Secure key-based SSH authentication is supported for both Linux and Windows, providing a streamlined and secure monitoring experience, while harnessing SSH’s exec functionality to avoid issues associated with interactive shell sessions.
Metrics covering utilization, VRAM usage, clock speeds and more help identify performance bottlenecks, as well as assists in identifying which models get the most from your hardware.
To simplify device management, the module introduces a dedicated PropertySource categorized as @category NVIDIA-SMI, ensuring a more organized and efficient monitoring process.
For more information, see NVIDIA SMI Monitoring in the product documentation.
Enhanced Script NetScans Now Groovy 4 Compatible
The following Enhanced Script NetScans for various platforms are now Groovy 4 compatible. For more information, see the product documentation:
Improved loader Snippet
The loader snippet now retrieves the latest snippet versions for API responses that are not using ZipCompression.
New lm.parse Snippet
To enhance collector performance, the new lm.parse snippet has introduced the getJsonStringNode
and getXMLStringNode
functions which search and extract nodes from JSON
or XML
as per the search string that you have specified.
Improved lm.observer Snippet
The lm.observer
snippet now reduces redundant cache lookups and ensures observerId
is set only when necessary. Cache management is improved by consistently updating the observer ID, enhancing efficiency and maintainability.
Improved lm.cache Snippet
The lm.cache
snippet now uses a direct import and static method call to access script cache. This change simplifies initialization and enhances code clarity.
Improved lm.topo Snippet
The updated lm.topo
snippet adds support for edge status.
Improved cisco.meraki.cloud Snippet
The updated cisco.meraki.cloud
snippet now expires unnecessary cached entries and allows for a configurable delay time between API calls.
Improved Cisco Meraki NetScan
The updated Enhanced Script NetScan for Meraki now checks for existence of Network ID key and duplicate devices when using CSV file.
For more information, see Cisco Meraki Monitoring in the product documentation.
Improved Cisco Catalyst Center NetScan
The updated Enhanced Script NetScan for Cisco Catalyst Center now uses a new endpoint for Catalyst Center version 2.3.7.6 and above. The Enhanced Script NetScan now groups devices by the site name hierarchy.
For more information, see Cisco Catalyst Center in the product documentation.
Apache Groovy 4 Support for all LogicMonitor-Provided LogicModules
In a future release, LogicMonitor Collectors will no longer support Apache Groovy 2. All official LogicMonitor-provided modules will be compatible with Apache Groovy 4. To support this migration, LogicMonitor will be releasing updates to official LogicModules to be compatible with Groovy 4.
As a result of this migration, you must do the following:
- Validate any customized or community-provided modules to ensure compatibility
For more information about validating your customized modules, see Custom Module Groovy Migration Validation in the product documentation. - Install a module update for LogicMonitor-provided modules that have compatibility changes released.
For more information, see LogicMonitor Provided Modules Groovy 4 Migration in the product documentation. - Update Enhanced Script NetScans to Groovy 4 compatible scripts.
For more information, see Enhanced Script NetScans Now Groovy 4 Compatible in the Modules section of the Release Notes.
For more information on the timeline of this migration, see Apache Groovy 2 End-of-Life Milestone Public Announcement].
The LogicMonitor EA Collector 34.500 or later is compatible with Groovy 2 and Groovy 4. For more information about the EA Collector release, see the EA Collector 34.500 Release Notes.
Note: Starting with the release of EA Collector 37.100, which is now available, the collector will utilize Groovy 4 instead of Groovy 2. In accordance with Collector versioning, a stable EA version is designated as an optional general release (GD).
When running a module using Apache Groovy 4, and using the groovy.json.JsonSlurper(), the following exception was with the LogicMonitor Collector version 36.200 or later.
exception:groovy.lang.RunTimeException: Unable to load FastStringService
When running a module using Apache Groovy 4, and the module includes an invalid type parameter for a data structure, the module throws the following exception:
java.lang.RuntimeException: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
Important: LogicMonitor is releasing updates to LogicModules to mitigate this issue for official LogicMonitor-provided modules.
When running a module using Apache Groovy 4, the following exception can be thrown when using the GroovyScriptHelper to incorporate LogicMonitor snippets in your script:
exception:groovy.lang.MissingPropertyException: No such property
To mitigate this issue, adjust the way the class is imported, similar to the following:
import com.santaba.agent.groovy.utils.GroovyScriptHelper
import com.logicmonitor.mod.Snippets
def modLoader = GroovyScriptHelper.getInstance(GroovySystem.version).getScript("Snippets", Snippets.getLoader()).withBinding(getBinding())
Important: LogicMonitor is releasing updates to official LogicModules to mitigate this issue for LogicMonitor-provided modules.
When running a module using Apache Groovy 4 with legacy classes in your script, the following exception can be thrown:
java.lang.RuntimeException: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed
To mitigate this issue, migrate to JPMS-compliant package names. Making this change does not break backward compatibility with Groovy 2.
For example, the following script uses legacy classes:
import groovy.util.XmlSlurper
import groovy.util.XmlParser
def xmlSlurper = new XmlSlurper()
def xmlParser = new XmlParser()
You can replace the legacy classes with JPMS-compliant package names in Groovy 4 to resolve the exception, similar to the following:
import groovy.xml.XmlSlurper
import groovy.xml.XmlParser
def xmlSlurper = new XmlSlurper()
def xmlParser = new XmlParser()
Important: LogicMonitor is releasing updates to LogicModules to mitigate this issue for official LogicMonitor-provided modules.
When running a module using Apache Groovy 4, and using java.util.Date.format(), the following exception was resolved with the LogicMonitor Collector version 35.400 or later.
import groovy.xml.XmlSlurper
import groovy.xml.XmlParser
def xmlSlurper = new XmlSlurper()
def xmlParser = new XmlParser()
Note: To resolve this issue when running a module using Apache Groovy 4, ensure you upgrade to the LogicMonitor Collector version 35.400 or later
In Apache Groovy 4, the behavior of the push() method for the List class is reversed. In Apache Groovy 2.4, the push() method would add an item to the list, in Apache Groovy 4 push() will work on the first item of a List.
// v4 Behavior
def numbers = [1, 2, 3, 4]
numbers.push(5)
println numbers
// OUTPUT: [5, 1, 2, 3, 4]
// v2.4 Behavior
def numbers = [1, 2, 3, 4]
numbers.push(5)
println numbers
// OUTPUT: [1, 2, 3, 4, 5]
To mitigate this issue, migrate to using add() in place of push():
def numbers = [1, 2, 3, 4]
numbers.add("5")
println numbers
// OUTPUT: [1, 2, 3, 4, 5]
When running a module using Apache Groovy 4, the behavior of the pop() method is reversed. In Apache Groovy 2.4 the pop() behavior would remove the last item in a list, in Groovy 4 pop() will remove the first item in a list.
// v4 Behavior
def numbers = [1, 2, 3, 4]
println numbers.pop()
// OUTPUT: 1
// v2.4 Behavior
def numbers = [1, 2, 3, 4]
println numbers.pop()
// OUTPUT: 4
To mitigate this issue, migrate to using remove() in place of pop():
def numbers = [1, 2, 3, 4]
println numbers.remove(numbers.size() - 1)
// OUTPUT: 4
Important: LogicMonitor is releasing updates to LogicModules to mitigate this issue for official LogicMonitor-provided modules.
NetScan
Legacy UI for NetScans Deprecation
As LogicMonitor continues to phase out the legacy UI, the New UI Preview switch will be removed for the NetScan Settings, making the settings unavailable using the legacy UI, and available in the new UI only. The new UI provides an enhanced user experience, improved performance, and security features.
Recommendation: To prevent disruption to your workflows, navigate to Settings > NetScan, and then toggle on the New UI Preview switch to familiarize yourself with the new UI and take advantage of the latest features and enhancements.
For more information about this deprecation, including timeline and further updates about the removal, see Notice for Upcoming Deprecation of Websites, Reports, and Settings pages from Legacy UI in LM Community.
For the most up-to-date information about NetScans, see NetScans Overview in the product documentation.
Note: This deprecation does not impact the availability of earlier versions of the Dashboards or Resources pages.
If you have any questions or require assistance during this process, contact the Support team or your Customer Success Manager.
Normalized Properties
Enhanced Support for Normalized Properties across Cloud Resources and other Devices
LogicMonitor has enhanced the Normalized Properties functionality to support grouping and filtering of all device types, including the cloud resources. Key benefits of this enhancement are as follows: * You can now consolidate resources from multiple cloud providers (such as AWS, Azure, and GCP) and devices into a single property alias, thus simplifying alert grouping and resource monitoring across all environments.
- You can now filter and group devices by normalized properties in the Resource Explorer, Dashboards, and Topology maps.
- You can add a maximum of 15 normalized properties, where the order of the properties determines their priority.
- This has streamlined monitoring across a broader range of resources and devices in LogicMonitor.
For more information, see Portal Settings in the product documentation.
Product Documentation
Enhanced Search Capabilities for Product Documentation
You can now refine your search results when searching for content within the LogicMonitor website, enabling you to filter your search results based on the type of content you want (for example, “Product Documentation”, “Release Notes”, and so on). This faceted search capability displays for search results in the Product Documentation and for the LogicMonitor website.
To access the filtered search capabilities, navigate to the Product Documentation landing page or the LogicMonitor website, and enter your search prompt. The filtering options display on your search engine results page.
Reports
Continued Support for Dynamic Links in Generated Reports
As a result of the Firebase Dynamic Links (FDL) deprecation, LogicMonitor is continuing to provide support for dynamic links for a generated report if you have disabled shared reporting in your LogicMonitor portal. If you have enabled shared reporting, LogicMonitor now displays the link as a text-wrapped link in the report history to allow for a condensed view of the link. You can expand the link as needed.
To access this link, navigate to Reports, select the report you want to view, and then select the History tab. The list of generated reports displays in a table format.
For more information about shared reporting, see Shared Report Access in the product documentation.
In addition, this enhancement resolves the intermittent error of “Dynamic Link Not Found” when generating an ad-hoc report.
Note: This enhancement applies to the new UI only. To take advantage of the latest features and enhancements and to prevent disruptions in workflows, navigate to Reports, and toggle on the New UI Preview switch.
For more information about the deprecation of Firebase Dynamic Links, see Dynamic Links Deprecation FAQ from Google.
Recommendation: For security best practices, restrict generated report access to logged-in users only to remove the dependency on publicly accessible short links. For more information, see LogicMonitor Security Best Practices in the product documentation.
Legacy UI for Reports Page Deprecation
As LogicMonitor continues to phase out the legacy UI, the New UI Preview switch will be removed from the Reports page, making Reports unavailable using the legacy UI, and available in the new UI only. The new UI provides an enhanced user experience, improved performance, and security features.
Recommendation: To prevent disruption to your workflows, navigate to Reports, and then toggle on the New UI Preview switch to familiarize yourself with the new UI and take advantage of the latest features and enhancements.
For more information about this deprecation, including timeline and further updates about the removal, see Notice for Upcoming Deprecation of Websites, Reports, and Settings pages from Legacy UI in LM Community.
For the most up-to-date information about Reports, see Choosing a Report Type in the product documentation.
Note: This deprecation does not impact the availability of earlier versions of the Dashboards or Resources pages.
If you have any questions or require assistance during this process, contact the Support team or your Customer Success Manager.
Note: Enforcement for your account may occur in a later version.
SaaS Monitoring
PagerDuty integration with SaaS is currently unavailable.
User Access
Legacy UI for User Message Templates Deprecation
As LogicMonitor continues to phase out the legacy UI, the New UI Preview switch will be removed for the User Message Templates, making the templates unavailable using the legacy UI, and available in the new UI only. The new UI provides an enhanced user experience, improved performance, and security features.
Recommendation: To prevent disruption to your workflows, navigate to Settings > Message Templates > User Messages, and then toggle on the New UI Preview switch to familiarize yourself with the new UI and take advantage of the latest features and enhancements.
For more information about this deprecation, including timeline and further updates about the removal, see Notice for Upcoming Deprecation of Websites, Reports, and Settings pages from Legacy UI in LM Community.
For the most up-to-date information about the User Message Templates, see Managing New User Message Templates in the product documentation.
Note: This deprecation does not impact the availability of earlier versions of the Dashboards or Resources pages.
If you have any questions or require assistance during this process, contact the Support team or your Customer Success Manager.
Legacy UI for User Access Settings Deprecation
As LogicMonitor continues to phase out the legacy UI, the New UI Preview switch will be removed for the User Access settings, making the settings unavailable using the legacy UI, and available in the new UI only. The new UI provides an enhanced user experience, improved performance, and security features.
Recommendation: To prevent disruption to your workflows and to familiarize yourself with the new UI and take advantage of the latest features and enhancements, navigate to Settings > User Access, and then toggle on the New UI Preview switch. You can navigate to and configure settings for Users and Roles, and Single Sign On in the new UI.
For more information about this deprecation, including timeline and further updates about the removal, see Notice for Upcoming Deprecation of Websites, Reports, and Settings pages from Legacy UI in LM Community.
For the most up-to-date information about User Access, see the following in the product documentation:
Note: This deprecation does not impact the availability of earlier versions of the Dashboards or Resources pages.
If you have any questions or require assistance during this process, contact the Support team or your Customer Success Manager.
Impact of the Back-end Infrastructure Updates
Due to the recent back-end infrastructure migration, during the creation of the training account, you may receive emails encrypted using the old method. After this update, if you select a link from an old email, it could lead to an error.
If this happens, you must submit a request to create a new training account. When you receive the new verification link, you can create the training account successfully.
Website Monitoring
Legacy UI for Websites Page Deprecation
As LogicMonitor continues to phase out the legacy UI, the New UI Preview switch will be removed for the Websites page, making Website Monitoring unavailable using the legacy UI, and available in the new UI only. The new UI provides an enhanced user experience, improved performance, and security features.
Recommendation: To prevent disruption to your workflows, navigate to Websites, and then toggle on the New UI Preview switch to familiarize yourself with the new UI and take advantage of the latest features and enhancements.
For more information about this deprecation, including timeline and further updates about the removal, see Notice for Upcoming Deprecation of Websites, Reports, and Settings pages from Legacy UI in LM Community.
For the most up-to-date information about Websites, see Websites Page Overview in the product documentation.
Note: This deprecation does not impact the availability of earlier versions of the Dashboards or Resources pages.
If you have any questions or require assistance during this process, contact the Support team or your Customer Success Manager.
Collector Releases
- EA Collector 37.100 was released on February 04, 2025. For more information, see the EA Collector 37.100 Release Notes.
- GD Collector 37.000 was released on January 27, 2025. For more information, see the GD Collector 37.000 Release Notes.
LogicModules Releases
New and updated LogicModules are available for you directly in your LogicMonitor portal. You can install new modules from the Exchange and update existing modules in My Module Toolbox. For more information, see Modules Installation, and Modules Management in the product documentation.
This section lists the LogicModules that are new in this release, updated in this release, or will be removed in a future release. Changes related to the LogicModule feature will be listed in the General Updates section.
New LogicModules
LogicModule Name | Details |
1 DataSource: – Microsoft_Azure_UpdateManager | Newly monitoring for Microsoft Azure Update Manager. |
1 DataSource: – Nvidia_SMI_SSH 1 PropertySource: – addCategory_Nvidia_SMI | LogicMonitor now provides support for monitoring NVIDIA GPUs. LogicMonitor’s Nvidia-SMI monitoring is optimized for fast efficient parsing, enabling scaleability to larger setups on a single collector with minimal impact to overall collector performance. Secure key-based SSH authentication is supported for both Linux and Windows, providing a streamlined and secure monitoring experience, while harnessing SSH’s exec functionality to avoid issues associated with interactive shell sessions.Metrics covering utilization, VRAM usage, clock speeds and more help identify performance bottlenecks, as well as assists in identifying which models get the most from your hardware.To simplify device management, the module introduces a dedicated PropertySource categorized as @category NVIDIA-SMI, ensuring a more organized and efficient monitoring process. For more information, see NVIDIA SMI Monitoring in the product documentation. |
Updated LogicModules
LogicModule Name | Details |
1 PropertySource: – Device_BasicInfo | Added debug messaging for devices that lack the system.sysinfo set. |
1 DataSource: – NetSNMP_Memory_Usage | Resolved an issue that caused devices to incorrectly report “no data” if they did not meet a condition checking for RHEL/CENTOS 7. |
1 DataSource: – Email_RoundTrip 1 DataSource: – Office365_Email_OAUTH | Added OAuth support for Office365. |
1 DataSource: -PaloAlto_Prisma_SDWAN_Underlay | Swapped instance wild alias and description to better align with Prisma UI and improve alert message. Added out of the box alerts for interface status. |
1 DataSource: – Microsoft_SQLServer_DatabaseStorage | Increased collection interval from 15 minutes to 60 minutes to reduce server impact. |
14 DataSources: – VMware_Horizon_ADDomains – VMware_Horizon_Applications – VMware_Horizon_Certificates – VMware_Horizon_ConnectionData – VMware_Horizon_Datastores – VMware_Horizon_DesktopPools – VMware_Horizon_EventDatabaseConnection – VMware_Horizon_LicenseInfo – VMware_Horizon_Machines – VMware_Horizon_PersistentDisks – VMware_Horizon_RDSServers – VMware_Horizon_Sessions – VMware_Horizon_Troubleshooter – VMware_Horizon_vSphereHosts | Added a check for availability of HorizonView module via Omnissa package. |
1 DataSource: – Dell_DRAC_AmperageProbe | Datapoints now have proper multipliers and units. Graphs are now dynamic and display the correct units for each probe. |
1 PropertySource: – addCategory_Cato_SDWAN | Updated to handle Cato SDWAN Socket serial numbers with case sensitivity, along with improvements to serial number matching and exception handling. Users must now enter exact, case sensitive Cato SDWAN Socket serial number in the ‘cato.api.device.serial’ property when adding Cato SDWAN Socket devices into monitoring. |
1 DataSource: – Cisco_Entity_Sensors | WARNING: Risk of historical data loss. If all high alerts are set to 0 and no low alerts exist, the instance will be deleted and historical data will be unavailable after 30 days.Does not display sensors with invalid thresholds set within the Cisco device to prevents false alerting. |
10 DataSources: – Cisco_Catalyst_AccessPointHealth – Cisco_Catalyst_AccessPointPerformance – Cisco_Catalyst_AccessPointRadios – Cisco_Catalyst_Center_API – Cisco_Catalyst_RouterHealth – Cisco_Catalyst_RouterPerformance – Cisco_Catalyst_SwitchHealth – Cisco_Catalyst_SwitchPerformance – Cisco_Catalyst_WLCHealth – Cisco_Catalyst_WLCPerformance 2 PropertySources: – addCategory_Cisco_Catalyst_Center_Device – addERI_Cisco_Catalyst_Center_Device 1 TopologySource: – Cisco_Catalyst_Center_Topology | Refactored to use a new endpoint for Catalyst Center versions 2.3.7.6 and above to resolve data gap issues for large environments. Added pagination for all endpoints to improve data collection for large environments. Removed all Health modules “healthy” datapoint as it reported inaccurate data and was not used for alerts. |