v.223 Release Notes

Filtering logic for instance properties in dashboards is now case-insensitive. Values such as “ABC”, “abc”, and “Abc” are treated as equivalent, preventing duplicate entries in filter drop-downs and ensuring consistent filtering behavior.

To access this improvement, navigate to a Dashboard and create a filter.

For more information, see Modern Dashboards in the product documentation.

You can now create Billing widgets in the LogicMonitor dashboard to visualize cloud cost information.

This widget provides several customized views of billing data at a glance. You can also drill down to more granular billing data within the widget, enhancing visibility of cloud spending.

To create a Billing widget, go to Dashboards and select Add Widget > Billing.

Access to the Cost Optimization product is required to create Billing widgets.

For more information, see Billing Widget in product documentation.

Fixed an issue that allowed a read-only API user to inadvertently create and delete a widget sharing link.

Fixed an issue that allowed an API user without proper permissions to bypass permission checks and delete a dashboard.

You can now configure LogicMonitor to connect to your ServiceNow instance using a full custom domain URL. This enables support for instances hosted on nonstandard or region-specific domains, enhancing compatibility for varied ServiceNow environments.

Previously, only the Subdomain field was available, requiring users to specify only the subdomain prefix of their ServiceNow instance (for example, dev for dev.service-now.com). With this new option, you can now toggle between subdomain-only and full domain configuration using the new Use Custom Domain URL switch.

For more information, see ServiceNow (Incident Management) Integration in the product documentation.

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 enhanced lm.data.topo snippet now blocks the Kubernetes Linux Calico MAC address. This prevents non-unique Calico MAC addresses from polluting topology data, improving the accuracy of network topology maps.

The enhanced VMware vSphere NetScan now places resources within the associated Root Folder in the Resource Tree. This enhancement improves resource organization.

For more information, see VMware vSphere Monitoring in the product documentation.

The cisco.ucs snippet now correctly escapes special characters in passwords. This enhancement ensures reliable authentication and prevents script execution failures due to unescaped characters.

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.

The LogicMonitor EA Collector 37.100, which is now available, will use 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 fixed 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 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]

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

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 

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, 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:

Fixed an issue that allowed a read-only API user to delete a report.

Creating an Alert report in CSV format with the maximum request threshold fails with the following error in logs: java.lang.OutOfMemoryError

You can now configure monitoring for various Artificial Intelligence (AI) and Large Language Model (LLM) products from a single onboarding page. This page allows you to explore all of the AI and LLM products that LogicMonitor supports, and quickly get started monitoring the services you need.

Navigate to Resource Tree in LogicMonitor and select Add > AI and LLMs to access the onboarding page.

In a future release of LogicMonitor, the support for LogicMonitor OpenTelemetry Collector 3.0.00 will be deprecated. Use the latest LogicMonitor OpenTelemetry Collector version.

For more information, see OpenTelemetry Collector Versions in the product documentation.