v.211 Release Notes

The Config Alerts Overview now provides detailed information about alerts generated for specific ConfigSource versions.

This enhancement offers greater visibility into configuration-related issues and their impact on your environment.

For more information, see Viewing Config Checks in our product documentation

Billing monitoring in Cost Optimization now supports the FOCUS 1.0 cost and usage schema for Azure exports.

A new widget tracking Resource Explorer data is now available in the LogicMonitor dashboard. Create new custom views or load from saved Resource Explorer views for quick access to summarize resource health. For more information, see Resource Explorer Widget

Note that resource explorer widgets do not support sharing via embedded URL. For more information on configuring Resource Explorer views, see Resource Explorer. For more information on configuring widgets, see Widget Creation.

The updated Enhanced Script NetScan for Cisco Meraki now uses the new recommended Meraki endpoint for retrieving data, replacing the previously deprecated endpoint.

For more information, see Cisco Meraki Monitoring in the product documentation.

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. The released updated modules are listed in the LogicModules Release section.
  For more information, see LogicMonitor Provided Modules Groovy 4 Migration in the product documentation.

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.

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]

Note: This issue is fixed with the LogicMonitor Collector version 35.400 or later. To mitigate this issue when running a module using Apache Groovy 4, ensure you upgrade to the LogicMonitor Collector version 35.400 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 runtime 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. If you are leveraging customized or community-provided modules, you must update the module to pass valid parameters into all data structures.

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. If you are leveraging customized or community-provided modules, you must update the module to pass valid parameters into all data structures.

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:

if(GroovySystem.version.startsWith(“2.”)) {
modLoader = com.logicmonitor.common.sse.utils.GroovyScriptHelper.getInstance()._getScript(“Snippets”, Snippets.getLoader())
} else {
modLoader = com.santaba.agent.groovy.utils.GroovyScriptHelper.getInstance(“v4”).getScript(“Snippets”, Snippets.getLoader())
}

For example, the following demonstrates how GroovyScriptHelper is used in Groovy 2:

import com.logicmonitor.common.sse.utils.GroovyScriptHelper as GSH
import com.logicmonitor.mod.Snippets

modLoader = GSH.getInstance()._getScript(“Snippets”, Snippets.getLoader()).withBinding(getBinding())

lmDebug = modLoader.load(“lm.debug”, “0”, true)
lmDebug.default_context = “Test:SettingContext”

You can modify the script to use the GroovyScriptHelper in Groovy 4, demonstrated in the following:

import com.logicmonitor.mod.Snippets

if(GroovySystem.version.startsWith(“2.”)) {
modLoader = com.logicmonitor.common.sse.utils.GroovyScriptHelper.getInstance()._getScript(“Snippets”, Snippets.getLoader())
} else {
modLoader = com.santaba.agent.groovy.utils.GroovyScriptHelper.getInstance(“v4”).getScript(“Snippets”, Snippets.getLoader())
}

lmDebug = modLoader.load(“lm.debug”, “0”, true)
lmDebug.default_context = “Test:SettingContext”

Important: LogicMonitor is releasing updates to official LogicModules to mitigate this issue for LogicMonitor-provided modules. If you are leveraging customized or community-provided modules, you must update the module to pass valid parameters into all data structures.

LogicMonitor has set a soft limit of 25% usage on the Alert Rules. For more information, see Limits, Quotas, and Constraints.