v.235 Release Notes

The Alerts table now displays an Alert Trigger Value column that provides the value which initially triggered a given alert. This enhancement provides improved visibility into the condition that caused the alert, enabling you to quickly assess potential causes.

This enhancement also supports the new ##TRIGGERVALUE## token for use in alert messages and notifications.

To customize the position of the Alert Trigger Value column in your alerts table, navigate to Alerts and select Show Table Settings. For more information on customizing alerts, see Managing Alerts from the Alerts Page in product documentation.

Cost Optimization Recommendations now detects idle GCP Compute Engine Virtual Machines, and recommends stopping or deleting idle VMs.

This enables you to easily identify Compute Engine VMs that are inactive or underutilized, and provides potential savings estimates from deleting those resources.

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

You can now rank metric results within label-defined groups directly in the Advanced Metrics widget. This reduces chart noise, ensures fair comparisons across collectors, platforms, regions, or tenants, and prevents large groups from dominating dashboard visualizations. This helps you build clearer, more focused dashboards in large or high-cardinality environments.

This enhancement leverages the topk by (label)(k, expression) and bottomk by (label)(k, expression) syntax queries, extending the topk(k, expression) and bottomk(k, expression) by ranking results independently per group defined in the BY clause. For example, topk(5, cpu_usage) returns the five highest series across all matching results based on the last value in the selected time range. In contrast, topk by (system.collectorid)(5, cpu_usage) groups series by system.collectorid and returns the top five per Collector. The widget displays full time trends for the selected series.

To access this functionality, navigate to Dashboards > create an Advanced Metrics widget, and use the “Bottom K by” or “Top K by” functions in the Query Builder of. Alternately, you can manually enter the queries using raw query.

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

• Advanced Metrics Widget
• LogicMonitor Query Language (LMQL) Reference

As LogicMonitor continues to phase out the legacy UI, the New UI Preview switch will be removed from Dashboards, making Dashboards unavailable using the legacy UI, and available in the new UI only. The new UI provides an enhanced user experience, improved performance, and security features.

For more information about this deprecation, including timeline and further updates about the removal, see Upcoming End-of-Life (EOL) for UIv3 Dashboards in LM Community.

For the most up-to-date information about Dashboards, see Dashboards Overview in the product documentation.

If you have any questions or require assistance during this process, contact the Support team or your Customer Success Manager.

You can now use the new Action Notes alert status for HTTP Delivery requests to update the Work Notes section of a ServiceNow incident ticket with a DiagnosticSource output report in JSON or plain text format.

LogicMonitor has also introduced the following tokens to configure the payload sent when a DiagnosticSource report is available for an alert:

• ##DIAGNOSTIC_SOURCE_OUTPUT##
• ##DIAGNOSTIC_SOURCE_STATUS##
• ##MESSAGE##

These tokens apply only to the Action Notes alert status for ServiceNow integrations.

For more information, see ServiceNow status in the product documentation.

The enhanced vmware.vsphere.api snippet now supports returning all monitored counters. You can retrieve a complete set of available performance metrics for your monitored VMware vSphere resources, which enables more comprehensive data collection and analysis.

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

The updated NetScan script now accounts for adding active switches and switch stack properties. You can discover and monitor active switches and associated stack details more accurately, which improves device visibility and data collection across your Cisco Meraki environment.

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

The enhanced lm.data.topo snippet now supports identification of Check Point Linux firewalls. You can automatically identify and map these firewalls in your topology data, which improves visibility into your network infrastructure.

The improved VeloCloud SD-WAN NetScan now script removes redundant parsing. This provides you with more experience more efficient script execution and improved performance during device discovery and data collection.

For more information, see Arista VeloCloud SD-WAN Monitoring in the product documentation.

You can monitor the health, capacity, and performance of Rubrik-managed clusters through Rubrik Security Cloud. You gain centralized visibility into cluster capacity, compression efficiency, and overall health without requiring direct access to individual Rubrik nodes. Webhook integration enables you to receive alerts and log data from Rubrik Security Cloud for timely awareness of events and issues.

The monitoring package uses the Rubrik Security Cloud GraphQL API to collect metrics and status information across all registered clusters. Data collection and alerting begin after the required LogicModules are imported.

To access this feature, navigate to Modules > Exchange and install the Rubrik Security Cloud Monitoring LogicModules.

For more information, see Rubrik Security Cloud Monitoring in the product documentation.

You can now monitor cloud-managed wireless access points deployed through CommScope’s RUCKUS One platform. This feature provides you visibility into access point health, inventory, client usage, and radio and SSID performance across venues, helping you better understand wireless availability and usage.

This feature uses the RUCKUS One public REST API to collect performance and inventory data. Monitoring begins after you import the required LogicModules and onboard access point resources.

To access this feature, navigate to Modules > Exchange and install the RUCKUS One AP monitoring package.

For more information, see Ruckus One AP Monitoring 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

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 EA Collector 39.100 , EA Collector 39.200 , EA Collector 39.300 and EA Collector 39.400 are now available and use Groovy 4 instead of Groovy 2. In accordance with Collector versioning, a stable EA version is designated as an optional general release (GD).
The GD Collector release planned for April 13, 2026, LogicMonitor GD Collector 39.004, 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 

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

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:

You can now include custom host properties in the Server CPU Report so you can deliver client-ready reports that combine CPU performance metrics with relevant resource metadata. This enhancement enables you to generate detailed CPU utilization reports directly from LogicMonitor, reducing the need for manual post-processing, lowering operational overhead, and improving scalability when supporting large customer environments.

The custom host properties display as custom columns alongside the minimum, maximum, and average CPU values across multiple resources in exported reports. You can save custom column selections as reusable report templates to support different reporting requirements across teams or customers.

To access this feature, navigate to Reports, and add a Server CPU report.

For more information, see Server CPU Report in the product documentation.

You can now configure the number of results that display in a Server CPU Report. This enables you to display the number of servers by CPU usage from a selection ranging from top 5, 10, 25, 50 or 100. In addition, you can display all results, which displays all available data based on the Resources or Resource Groups you define in the report.

To access this feature, navigate to Reports, and add a Server CPU report.

For more information, see Server CPU Report in the product documentation.

In the Service Naming Pattern of an existing Service Auto-Creation Rule, you can now edit the Prefix and Suffix values. Previously, users could not modify the naming pattern without recreating the rule and associated services from the beginning.

This enhancement improves flexibility by allowing cosmetic updates to service names without affecting cardinality properties or grouping logic. This change applies only to Prefix and Suffix values. However, the Grouping logic and cardinality properties remain unchanged and continue to follow the existing rule modification restrictions.

To edit the naming pattern, navigate to Services > Service Auto-Creation Rules, select the rule, and update the Service Naming Pattern field.

For more information, see Adding Services Using Auto Creation Rules in the product documentation.

In a future release of LogicMonitor, support for legacy LM Container builds and Argus versions 5, 6, 7, and 8 will be discontinued. If you are running these versions, upgrade to a supported LM Container release to continue receiving updates and support.

The latest LM Container releases provide:

• Improved monitoring accuracy through updated and actively maintained code paths

• The latest security patches and compliance updates required for modern Kubernetes environments

• Ongoing compatibility with newer Kubernetes versions and container runtimes

For more information about this deprecation, including timeline and further updates about the removal, see Upcoming End of Life (EOL) for Legacy Versions 5, 6, 7, and 8 for Legacy LM Container & Argus in the LM Community.

If you have any questions or need assistance during this transition, contact the Support team or your Customer Success Manager.