v.219 Release Notes
Last updated on 27 March, 2025Account Information
Improved Billing Information for Account Information
We’ve made key improvements to the Billing Information section under Account Information to enhance clarity and user experience:
- Disclaimer Placement Update: The 12-month invoice history disclaimer now appears above the invoice table, providing helpful context before users review their invoices.
- $0 Invoice Info Icon: A new info icon has been added next to the download option for $0 invoices.
- Tooltip for $0 Invoices: Hovering over the icon reveals a tooltip explaining that PDFs are not automatically generated for $0 invoices, offering instant guidance.
- Non-Clickable Invoice Numbers: Invoice numbers without associated invoices are now shown as plain text (no underline or link), making it clear they are not clickable.
These changes are designed to create a more intuitive and informative billing experience for users.
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.
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
New Cost Optimization Recommendations Actions
You can now acknowledge, snooze, ignore, or set to active the recommendations generated by the Cost Optimization Recommendations feature.
This allows you to prioritize the most impactful recommendations, while managing the amount of detail you see in your active recommendations list.
For more information, see Cost Optimization – Recommendations in product documentation.
Dashboards
Security Enhancements for Text Widget
LogicMonitor has upgraded the text editor used in the Text widget to mitigate the potential security vulnerabilities and to provide an enhanced user experience.
The following enhancements are made to the text editor:
- The text editor now displays word and character count, providing visibility for your total words and characters.
- You can now resize cells by dragging the rows and columns in a table.
- Font size now leverages headings in various sizes (normal and headings 1-4).
- When adding an image, you can now drag the image to the size you need in addition to resizing by entering pixel width and height.
This enhancement resolves the “This CKEditor 4.19.1 version is not secure” error displayed in the text editor.
For more information, see Text Widget in the product documentation.
Recommendation: To familiarize yourself with the new UI and benefit from the latest features and enhancements, navigate to Dashboards, and then toggle the New UI Preview switch.
Integrations
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
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 Cisco Meraki NetScan
The improved Meraki NetScan now supports Meraki tags, which will appear in LogicMonitor as a new device property: meraki.network.tags. This enhancement provides better visibility and organization of Meraki devices within LogicMonitor.
Improved lm.data.topo Snippet
The improved lm.data.topo snippet now sets predef.externalResourceType to ‘Wireless’ for Aruba OS devices. Additionally, the new regex patterns now has the improved ability to identify Cisco routers, ensuring that predef.externalResourceType is correctly set to ‘Router’ for more Cisco devices.
Improved VMware vSphere NetScan
The updated Enhanced Script NetScan for VMware vSphere Monitoring adds support for the optional property vcenter.ignore.proxy. Set it to “true” if you want to use a proxy for LogicMonitor but not your vCenter hosts.
For more information, see VMware vSphere Monitoring 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: GD Collector 37.003, which will be available in April 2025, will utilize Groovy 4 instead of Groovy 2. In accordance with Collector versioning, a stable GD version is designated as Required General Release (MGD).
When running a module using Apache Groovy 4, and using the groovy.json.JsonSlurper(), the following exception was fixed with the LogicMonitor Collector version 36.200 or later:
exception:groovy.lang.RunTimeException: Unable to load FastStringService
Note: Note: To mitigate this issue when running a module using Apache Groovy 4, ensure you upgrade to the LogicMonitor Collector version 36.200 or later.
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
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.
exception:groovy.lang.MissingMethodException: No signature of method: java.util.Date.format() is applicable for argument types: (String) values: [yyyy-MM-dd'T'HH:mm:ss z]
Note: To mitigate 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.
Reports
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.
User Access
Security Enhancement for New User Message Templates
LogicMonitor has upgraded the text editor used in the New User Message template in Settings to mitigate potential security vulnerabilities and to provide an enhanced user experience.
As a result of this security upgrade, the following enhancements have been made to the text editor:
- A word and character counter is now displayed in the text editor, providing visibility for your total words and characters.
- You can now resize cells in a table by dragging the rows and columns to the size you need.
- Font size now leverages headings in various sizes (normal and headings 1-4).
- When adding an image, you can now drag the image to the size you need in addition to resizing by entering pixel width and height.
This enhancement resolves the “This CKEditor 4.19.1 version is not secure” error displayed in the text editor when editing the New User Message template.
For more information, see New User Message Teamplate in the product documentation.
Recommendation: To familiarize yourself with the new UI and take advantage of the latest features and enhancements, navigate to Settings, and then toggle on the New UI Preview switch.
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.
Website Monitoring
Improved Data Aggregation for Websites
For better performance and scalability, LogicMonitor has now streamlined data handling with the overall checkpoint data having a single entry of aggregated data per polling interval. Previously, overall checkpoint data contained aggregated data derived from individual checkpoint data, with multiple entries for the same polling interval. For more information, see Data Monitored for Websites.
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
GD Collector 37.001 was released on February 19, 2025. For more information, see the GD Collector 37.001 Release Notes.
Container Monitoring Releases
Enhanced _deleted Group
The _deleted group, which tracks deleted Kubernetes devices, will transition from a dynamic to a static configuration. This update, set to be rolled out in upcoming releases, is designed to enhance system stability and provide more effective retention control.
Optimized Kubernetes Monitoring
Resource monitoring in Kubernetes clusters is now optimized to reduce unnecessary system strain, particularly for new installations and cache refresh scenarios. By default, only critical resources are monitored, while non-essential resources are filtered or disabled.
To improve efficiency, Kubernetes now excludes temporary resources like Jobs, CronJobs, and their related Pods from monitoring. Non-compute resources in OpenShift namespaces are also excluded. Additionally, monitoring for ConfigMaps and Secrets is turned off by default but can be re-enabled through Helm chart filter updates. When upgrading from a previous Helm chart version, any existing custom filters and disabled monitoring settings remain unchanged. Default settings only apply if no custom configurations exist.
For more information, see Default Filtering for Kubernetes Resources in the product documentation.
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 TopologySource: – Cisco_Meraki_SwitchStack_Topology | New TopologySource to handle switch stack topology. |
1 TopologySource: – Cisco_Meraki_Switch_Topology | Added support for Cisco Meraki switch topologies. |
1 DataSource: – AWS_Amazon_QBusiness | New Datasource for Amazon Q Business. |
2 LogSources: – Juniper Mist Client Events – Juniper Mist Device Events | Added support for Juniper Mist Wireless Client and Device event LogSources. |
Updated LogicModules
LogicModule Name | Details |
1 TopologySource: – Cisco_Meraki_Topology | Break up switch stack topology and SDWAN topology to handle edge status payload difference. |
1 DataSource: – LogicMonitor_Collector_Snippets | Updated to check for latest loader version. |
1 PropertySource: – addCategory_Cisco_Catalyst_Center_Device | Added support to auto detect when no system.categories set and make API calls necessary to apply them out of the box for manually added devices. |
1 PropertySource: – addCategory_Cisco_Meraki_Device | Meraki tags will now be represented in LogicMonitor as a device property ‘meraki.network.tags’. |
1 PropertySource: – addERI_Cisco_Catalyst_Center_Device | Added CDP displayname ERI. |
1 PropertySource: – addERI_PaloAlto | Support MAC ERI setting for active-primary, active-active setups. |
2 DataSources: – Juniper_Mist_SDWAN_Edge_Health – Juniper_Mist_Switch_Health | Resolved an issue causing devices without a local collector to incorrectly report as dead. Updated the polling interval to 1 minute, ensuring these devices have host status accurately reported. When using the Juniper Mist Suite the health module should be utilized to alert devices as down. |
2 DataSources: – Sophos_XG_HAStatus_v18+ – Sophos_XG_Stats_v18+ | Module display name has been updated to adhere to style guidelines. |
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 | Resolving issue that was resulting in properties not to be output if cisco.catalyst.center.device.id had not been previously set. Added support for checking device status by overall health and new field ‘connectionStatus’ for Catalyst Center version 2.3.7.6 and above. |
1 DataSource: – Cisco_Meraki_Switches | Update Active Discovery to add all Cisco switch models with product type “switch”. |
1 ConfigSource: – SonicWall_SonicOS | Added a regex filter to ignore lines starting with ‘date’. |
1 DataSource: – Linux_SSH_NetworkInterfaces | Interfaces that are consistently down will be filtered out during active discovery to prevent unnecessary alerts. Additionally, instances will no longer be automatically deleted, ensuring that those that were previously up but later go down are not mistakenly removed. |
1 DataSource: – Apache- | Deprecated datapoint metric type was causing issue when trying to clone. Updated ‘status’ datapoint’s metric type to fix. |
20 DataSources: – Cisco_Meraki_API – Cisco_Meraki_AccessPointHealth – Cisco_Meraki_AccessPointPerformance – Cisco_Meraki_AccessPointRadios – Cisco_Meraki_AccessPointSSIDs – Cisco_Meraki_CameraHealth – Cisco_Meraki_CellularGatewayHealth – Cisco_Meraki_CellularGatewayPerformance – Cisco_Meraki_DeviceInterfaces – Cisco_Meraki_DoorSensor – Cisco_Meraki_IndoorAirQualitySensor – Cisco_Meraki_PowerSensor – Cisco_Meraki_SecurityApplianceHealth – Cisco_Meraki_SecurityAppliancePerformance – Cisco_Meraki_SecurityApplianceTunnels – Cisco_Meraki_SecurityApplianceUnderlay – Cisco_Meraki_SwitchHealth – Cisco_Meraki_SwitchInterfaces – Cisco_Meraki_SwitchPerformance – Cisco_Meraki_TemperatureSensor 2 PropertySources: – addCategory_Cisco_Meraki_Device – addERI_Cisco_Meraki_Device 2 TopologySources: – Cisco_Meraki_LinkLayer_Topology – Cisco_Meraki_Topology | This update increases the scalability and performance of Cisco Meraki Switch port monitoring by migrating from the per-device getDeviceSwitchPortsStatuses Meraki Dashboard API endpoint to the per-organization getOrganizationSwitchPortsUsageHistoryByDeviceByInterval and getOrganizationSwitchPortsStatusesBySwitch endpoints. The change also includes cache optimization improvements for the entire Meraki package. |
1 DataSource: – Cisco_Catalyst_SDWAN_Tunnels 1 TopologySource: – Cisco_Catalyst_SDWAN_Topology | Added support for edge status. |
1 DataSource: – Cisco_Catalyst_SDWAN_API 5 PropertySources: – addCategory_ArubaEdgeConnectSDWAN – addCategory_Cato_SDWAN – addCategory_Cisco_Catalyst_SDWAN – addCategory_Juniper_Mist_Device – addCategory_Versa_SDWAN_Appliance | Added support to auto detect when no system.categories set and make API calls necessary to apply them out of the box for manually added devices. |
5 ConfigSources: – SCP_Standard – SFTP_Standard – SSH_Exec_Standard – SSH_Interactive_Standard – Telnet_Interactive_Standard | Common Configs now ignore whitespace changes when alerting. |
1 DataSource: – SNMP_Network_Interfaces | Added an optional ‘interface.wildalias.ifname’ property. This can fix the potential issue of blank instance names if the interfaces don’t have a description. To have the WildAlias determined by ifName instead of ifDescr, set the host property **interface.wildalias.ifname** to **true**. |
1 PropertySource: – Config_Cisco_Generic | The AppliesTo logic has been updated to include additional Cisco Catalyst Switches that lack generic system information. |
1 ConfigSource: – FTP_Files | Revamped and tidy both AD and Collect scripts to connect via both FTPClient and URI methods and Simplified script workflow. |
24 DataSources: – Cisco_UCS_BladeServerComponents – Cisco_UCS_BladeServers – Cisco_UCS_Chassis – Cisco_UCS_ChassisPorts – Cisco_UCS_ChassisUtilization – Cisco_UCS_Disks – Cisco_UCS_FEXPorts – Cisco_UCS_FIStoragePartitions – Cisco_UCS_FabricExtender – Cisco_UCS_FabricInterconnect – Cisco_UCS_Fans – Cisco_UCS_Faults – Cisco_UCS_IMCDisks – Cisco_UCS_IOCards – Cisco_UCS_PSUs – Cisco_UCS_Ports – Cisco_UCS_RackServerComponents – Cisco_UCS_RackServers – Cisco_UCS_SANPortChannels – Cisco_UCS_ServerInterfaces – Cisco_UCS_ServiceProfiles – Cisco_UCS_Sessions – Cisco_UCS_VLANs – Cisco_UCS_VSANs 2 PropertySources: – addCategory_Cisco_UCS – addERI_Cisco_UCS 1 TopologySource: – Cisco_UCS_Topology | Updated suite to be sensitive to the ‘proxy.enable’ property that could be set on the device. If the ‘proxy.enable’ property is set to false, it will ensure that no proxy is used when making the HTTP request. |
1 DataSource: – PaloAlto_FW_QoS_V9+ | The PaloAlto_FW_QoS_V9+ (which originally only supported software-based devices) have been updated to support all currently known Palo Alto hardware-based devices: * PA-32 (all devices in the PA-32XX range) * PA-52 (all devices in the PA-52XX range) * PA-5450 (a single, specific device) * PA-70 (all devices in the PA-70XX range) * PA-75 (all devices in the PA-75XX range) The module also supports the “paloalto.append.hardware.models” device property. If your hardware based model is not represented in the above list, you can add it as a comma separated value to the “paloalto.append.hardware.models” property on the device. |
4 DataSources: – VMware_vCenter_Alerts – VMware_vCenter_HostInterfaces – VMware_vCenter_HostPerformance – VMware_vCenter_HostVSwitch | Refactored to use improved VMWare snippet, allowing for multiple auth credential failover depending on if resource is an ESXi host or vCenter Appliance. |
2 DataSources: – Juniper_Mist_API – Juniper_Mist_AP_Radios | Added support for Juniper Mist Wireless Client and Device event LogSources. |