v.225 Release Notes

LogicMonitor now supports monitoring for Azure Container Apps.

When you add a container application, LogicMonitor automatically detects it and starts monitoring its health without additional configuration.

For more information, see Cloud Services and Resource Units in the product documentation.

LogicMonitor now supports monitoring for Azure Container Instances.

When you add a container instance, LogicMonitor automatically detects it and starts monitoring its health without additional configuration.

For more information, see Cloud Services and Resource Units in the product documentation.

You can now visualize multiple billing dimensions at the same time by selecting Sunburst as a visualization type when creating a Billing widget in LogicMonitor Dashboards.

This new chart enables you to compare multiple dimensions of cost data in a single donut-style view.

Sunburst visualizations make it easy to identify top spend drivers across dimensions, see cost distribution in a multi-layered format, and quickly explore hierarchical data without switching views.

For more information, see Billing Widget in product documentation.

The Billing widget in LogicMonitor Dashboards now enables you to view a selected widget dimension in Resource Explorer using the Drill Down menu. Alternatively, you can apply the selected dimension directly to dashboard-level filters.

These options improve the flexibility of Billing widget visualizations when monitoring costs in a specific context (such as individual regions, accounts, or environments.)

For more information, see Billing Widget in product documentation.

LogicMonitor has increased the resource instance limits for the following widgets:

• Gauge
• Big Number
• Pie

This enhancements enables you to visualize and monitor more instances per widget. This allows for more coverage and comprehensive insights—particularly in environments with high instance density.

To create these widgets, navigate to Dashboards, and add a widget.

LogicMonitor has enhanced the LM Logs platform with the ability to track aggregate queries through saved searches, providing deeper observability and custom metricization capabilities. You can now enable query tracking for aggregate log queries, in addition to basic queries. This allows you to:

• Transform log search results into time series metrics
• Automatically generate DataSources that track log-derived metrics at 5-minute intervals
• Use dynamic datapoints derived directly from your aggregate query output

This enhancement enables teams to convert log data into metrics, visualize trends, correlate log activity with system performance, and build alerting on log-derived metrics.

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

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