The following Enhanced Script NetScans for various platforms are now Groovy 4 compatible. For more information, see the product documentation:

• VMware vSphere Monitoring
• VMware SD-WAN Monitoring
• Versa SD-WAN Monitoring
• Aruba EdgeConnect SD-WAN
• Cisco Catalyst SD-WAN Monitoring
• Cisco Meraki Monitoring (Legacy)
• Cisco Meraki Monitoring
• Cisco Catalyst Center
• Juniper Mist Monitoring
• Palo Alto Prisma SD-WAN Monitoring

The updated Enhanced Script NetScan for Juniper Mist now ensures that the External IP is used as the hostname in NetScan when there’s a mismatch between the device’s IP and External IP.

For more information, see Juniper Mist Monitoring in the product documentation.

The updated cisco.meraki.cloud snippet has improved debug messaging.

Updated lm.remote snippet to be Groovy 4 compatible.

Updated lm.stats snippet to be Groovy 4 compatible.

The updated cisco.catalyst.center snippet improves pagination and caching for Cisco data retrieved via API.

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 v.214 Modules 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 in December of 2024, the collector will utilize Groovy4 instead of v2. 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 is thrown:

exception:groovy.lang.RunTimeException: Unable to load FastStringService

Note: This issue is fixed with the LogicMonitor Collector version 36.200 or later. 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:|

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())

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()

When running a module using Apache Groovy 4, and using java.util.Date.format(), the following exception is thrown:

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]

The Config alert email includes a direct link to view the changes made in the Config file.
This enhancement enables you to identify and address issues quickly.
For more information on Config Checks, see Viewing Config Checks in our product documentation.

Edge Status provides real-time network health insights on the topology map. It visualizes current latency metrics through mouseover and dynamically colors edges based on their performance.

Note: The Edge Status feature is available only for Routing connection types. In addition, the Edge Status feature is available only for the following TopoSources and DataSource:

TopoSources

• Cisco_Meraki_Topology

DataSource

• Cisco_Meraki_SecurityApplianceTunnels

To view the Edge Status feature, navigate to LogicMonitor portal > Mappings > Saved Maps and select a saved map. For more information, see Topology Edge Status in our product documentation.

As part of our ongoing efforts to improve the overall user experience and streamline our platform, we are announcing the upcoming deprecation of the Websites on legacy UI.

What should you do?

• Migrate to New UI:  We encourage you to migrate to our new UI for enhanced features and a more intuitive interface.
• Contact Support: If you have any questions or require assistance during the migration process, contact our Support team or your Customer Success Manager.

Documentation link for new UI: Websites