v.231 Release Notes

To make the Alert Details page informative and user-friendly, LogicMonitor has implemented the following UI and design enhancements:

Overview tab—Consolidated duplicate alert metadata and made the alert datapoint graph easily visible.

• Moved additional metadata for alerts to the Show alert metadata section.
• Display an overview of datapoint analysis in the Show datapoints analysis insights section.

Graphs tab—You can now view graphs from multiple datasources within the alert details.

• The Show graphs from dropdown menu enables you to view alert-time graphs for each datasource instance attached to the resource.

History tab—You can now select the any bar in the graph to view all alerts in a table format for the selected time period.

For more information, see Managing Alerts from the Alerts Page in the product documentation.

LogicMonitor now supports rebalancing ABCGs based not only on instance thresholds but also on resource property values. When you enable the Property Based Balancing switch, the  auto.collector.site.affinity.id property is auto-populated in the Property Name field by default. This property mitigates API Rate limiting with Cisco Meraki, Catalyst Center, Catalyst SD-WAN, Ruckus One, and Juniper Mist by keeping resources with matching network or site IDs on the same Collector.

In v231 Platform release, this feature is available to select early adopter customers and will become generally available in subsequent releases. 

For more information, see Auto-Balanced Collector Groups in the product documentation.

Cost Optimization Recommendations now detects idle Azure Load Balancers, and recommends deleting unneeded load balancers.

This enables you to easily identify load balancers that are inactive, and provides potential savings estimates from deleting those resources.

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

You can now add instance properties in a Table widget to display, sort, and filter the data at the instance-level metrics. This provides more contextual dashboards by exposing instance-level metadata such as WAN link identifiers, database types, or process names directly within the table view.

Instance properties can help reduce troubleshooting time by identifying underperforming interfaces, databases, or processes without drilling into each host. It also eliminates the need for workarounds such as concatenating resource and instance tokens to simulate multi-level sorting.

To access this feature, navigate to Dashboards > Add Widget > add a Table widget. You can add instance properties to a Dynamic Table after configuring a datapoint.

For more information, see Table Widget in the product documentation.

You can now perform various interactions on an Advanced Metrics widget that is added to a Dashboard. This provides you with more flexible actions when interacting with widgets, enabling you to engage in active troubleshooting more efficiently. For example, for data displayed as a Pie Chart, you can select a specific slice of the pie chart and navigate directly to the corresponding Resources in the Resource Tree to view the data for that instance.

To access this feature, navigate to Dashboards, and add an Advanced Metrics widget to the Dashboard.

For more information, see Advanced Metrics Widget in the product documentation.

ConnectWise Integration now automatically populates the configuration field on service tickets generated by resource alerts.

This enhancement identifies which devices or configurations generated the alert without additional input during ticket creation.

For more information, see ConnectWise Integration in product documentation.

LogicMonitor now introduces LogPilot, a new AI-powered query-less logs experience in LM Logs. With LogPilot, you can retrieve and analyze logs using natural language—no log query expertise required. Whether investigating alerts, building regex-based searches, or optimizing existing queries, LogPilot accelerates troubleshooting by translating plain English into precise, actionable results.

To access this feature, navigate to Logs and select Help me write query.

For more information, see Natural Language Querying in LM Logs 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 improves regex matching to correctly map resources containing “access point” in system information to the Wireless ERT. The improved regex also correctly aligns Meraki MR devices and other AP models with the Wireless ERT.

The enhanced Cisco UCS X-Series NetScan now uses the first IP to discover resources and ensure they are added to the portal.

For more information, see Cisco UCS X-Series Modular System Monitoring in the product documentation.

The enhanced velocloud.sdwan snippet improves how topology processes edge status and edge events API calls so you can retrieve accurate and consistent SD-WAN data.

The enhanced lm.remote snippet can now identify broken connections and attempt a reconnect during sequential interactions. You can maintain continuity when working with unstable connections or with devices that close sessions after specific actions.

The enhanced cisco.meraki.cloud snippet improves how modules handle the {} “Please reduce timespan” error message so you can review clearer debug and log messages during troubleshooting.

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 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, use Groovy 4 instead of Groovy 2. In accordance with Collector versioning, a stable EA version is designated as an optional general release (GD).

In December, LogicMonitor EA Collector 39.100, will use Groovy 4 instead of Groovy 2.

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

Fixed an issue that caused data collection failures when the Cisco DNAC integration generated paginated API requests. The EventSource added a “?” to URLs that already contained query strings, which produced HTTP 404 errors.

URLs now concatenate pagination parameters with “&” so you can collect data without interruption.

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:

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

You now have improved visibility and control when reviewing configuration versions in the Configs tab. The updated experience displays configuration details more clearly, highlights differences more intuitively, and provides streamlined access to comparison tools and alert context. These enhancements make it easier to identify configuration changes, understand their impact, and take action quickly.

To access the feature, navigate to Resources > Configs for any resource with a ConfigSource enabled.

For more information, see Configs Tab 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.