v.226 Release Notes

To ensure consistent behavior and prevent issues with glob expression pattern matching, certain special characters can no longer be used in the escalation chain and alert rules names. The following characters are now restricted from the Name field when adding escalation chains and alert rules:
* ? [ ] ( ) ! | \ "

If you had created escalation chains or alert rules with the newly prohibited characters in their names in V225 or prior, you must remove those characters before saving any further updates.

For more information, see Escalation Chains and Alert Rules in the product documentation.

You can now identify idle AWS RDS instances and see recommendations to back up and terminate them. This enables you to reduce unnecessary costs from unused databases.

For more information, see Cost Optimization – Recommendations in the product documentation.

LogicMonitor has added a Manage Billing Configurations tool to Cost Optimization Billing that enables you to configure your AWS and Azure billing data exports. This streamlines the process of exporting cloud billing data from each provider into LogicMonitor.

LogicMonitor continues to support the existing configuration method using  Resource Tree at this time, and previously configured billing exports will still appear in Cost Optimization – Billing.

For more information, see Cost Optimization Billing Configuration in the product documentation.

You can now dynamically parse structured JSON data in logs using the enhanced json operator. Instead of automatically flattening nested JSON fields at ingestion, LogicMonitor now stores them as serialized JSON strings and enables you to extract only the fields you need at query time. This update improves performance, reduces storage overhead, and enables greater query flexibility.

As part of this change, LogicMonitor will deprecate automatic JSON flattening for log fields at ingestion. Fields no longer will expand into multiple dot-notated keys (field.subfield) such as array.0 or metadata.user.name during processing. You must use the json operator to access nested data within serialized JSON fields.

The enhanced json operator flattens a specified JSON field on demand and supports runtime field extraction using dot notation.

For more information, see Advanced Search Operators 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 lm.topo snippet now supports null values for the from and to instances in the generateTopology() function. Additionally, it now supports namespace values that include commas.

The Enhanced Script NetScan for Juniper Mist Monitoring now includes the MacAddress property during onboarding. This enables support for device deduplication, improving accuracy in resource discovery.

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

LogicMonitor now supports uploading MIB files for SNMP Trap log ingestion using the SNMP Trap MIBs feature. When you upload a MIB file and its dependencies, LogicMonitor automatically validates the files, and uses them for SNMP trap translation.

To upload a MIB file, navigate to Settings > SNMP Trap MIBs.

For more information, see SNMP Trap MIBs 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 is 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 Collectors 37.100, 37.200, and 37.300 which are 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:

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]

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

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

You can now create an Alert report after configuring the filters on the Alerts page to display the relevant alerts you need. This enhancement prevents you from having to recreate alerts filters when configuring your Alert report.

To access this feature, navigate to Alerts. Use the filters to display the alerts you need, and then select Create an Alert Report. You are redirected to Reports with an Alert report preconfigured with the alerts you filtered from the Alerts page.

For more information, see the following in the product documentation:

• Alerts Report
• Managing Alerts from the Alerts Page

You can now preset the number of days after which the Enable Remote Session and Enable Test Script switches are automatically disabled. By default, these switches remain disabled. When you enable the switch, a dropdown menu displays, enabling you to select the disable-after duration.

If the Enable Remote Session and Enable Test Script switch is already enabled in V225 or earlier, then the disable-after duration is automatically set to ‘Never’.

For more information, see Security Settings in the product documentation.

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.

All users except SAML, API-only, and LM Support users can now self-activate their accounts when suspended due to inactivity. This applies only if your account was suspended for inactivity in version V224 or later.

Previously, activating inactive accounts required backend support for recovery. You can now recover suspended accounts due to inactivity without backend support. If you are locked out, you will receive an email with a recovery link to reset your password and regain access, ensuring continued portal availability.

For more information, see Security Settings in the product documentation.