LogicMonitor now supports GCP High Availability VPN Gateways. For more information on supported cloud resources, see Cloud Services and Resource Units in the product documentation.

Added new category for SaaS Lite Monitoring. Created SaaS_PageryDuty_Status module and the service to provide SaaS Lite Pagerduty status service coverage.

You can now use the asterisk (*) wildcard character to refine resource searches within the Dashboard. To use this feature, navigate to Dashboards > Filters > Resource Name.

For more information, see Creating Dynamic Filters in the product documentation.

The updated lm.topo snippet supports edge status functionality for topology.

The following Enhanced Script NetScans for various platforms are now compatible with Groovy 4. 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 will release 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 supported 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.

Note: Starting with the release of EA Collector 37.100, which is now expected in February 2025, the collector will utilize Groovy 4 instead of Groovy 2. In accordance with Collector versioning, a stable EA version is designated as an optional general release (GD).

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

Important: LogicMonitor is releasing updates to LogicModules to mitigate this issue for official LogicMonitor-provided modules.

When running a module using Apache Groovy 4, and using java.util.Date.format(), the following exception is 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]


Note: This issue is fixed with the LogicMonitor Collector version 35.400 or later. To mitigate this issue when running a module using Apache Groovy 4, ensure you upgrade to the LogicMonitor Collector version 35.400 or later

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

Important: LogicMonitor is releasing updates to LogicModules to mitigate this issue for official LogicMonitor-provided modules.

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

Important: LogicMonitor is releasing updates to official LogicModules to mitigate this issue for LogicMonitor-provided modules.

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:

Important: LogicMonitor is releasing updates to LogicModules to mitigate this issue for official LogicMonitor-provided modules.

When running a module using Apache Groovy 4, and using the groovy.json.JsonSlurper(), the following exception is thrown:

exception:groovy.lang.RunTimeException: Unable to load FastStringService

Note: This issue is fixed with the LogicMonitor Collector version 36.200 or later. To mitigate this issue when running a module using Apache Groovy 4, ensure you upgrade to the LogicMonitor Collector version 36.200 or later.

The alert tuning tab has a new and improved Threshold Editor, presented in a new modal with a fullscreen toggle and updated title.

The new improvements include the following:

• The title displays the DataSource name, followed by the datapoint name and the level being edited
• New calendar legend
• Clearer, more intuitive alerting parameters
• “Set At/Inherited From” field for quick visibility into existing thresholds
• Warning messages for overwritten or inactive thresholds caused by user changes and threshold cloning
• Static threshold settings are now located in a separate, focused form
• These forms include context tables for better clarity
• Improved history records and Alert routing cards now feature links to both the alert rule and escalation chain for the given datapoint
• Improved user experience by providing a more efficient threshold configuration process, navigation, and validation for a smoother workflow

When you select on a device, on the Resources page, the breadcrumb navigation includes static group over dynamic group. If only dynamic group exists for the device, then dynamic group with the lowest ID is used in the breadcrumb.

Refer to the following scenario as an example.

Production Datacenter Servers (static group): 5 devices including server123
Devices by Type > Linux Servers (dynamic group): 55 devices including server123

In this scenario, if you select server123, on the Resources page, the breadcrumb navigation displays Production Datacenter Servers (static group) > server123.

You can now view logs associated with a specific trace directly from the Trace Timeline page. When you select a span, the corresponding logs for that trace ID are displayed under the Logs tab. In addition, if the logs do not have the trace ID, the system searches for logs within the selected time window (For example, 10 minutes) before and after the ingestion time of the span.

For more information, see Viewing Traces Data in the product documentation.

Changes to the tenant identifier on the LogicMonitor platform will be reflected in the Tracing Usages Processor after a 30-minute delay due to caching. During this time, usage data will be reported with the old tenant identifier without any data loss.

There is no immediate workaround. Manual verification of the tenant data is advised.

You can now view the usage data for devices, websites, and wireless access points that your account monitors. This gives you the insight to manage cost in your environment.

LogicMonitor displays a table listing each account with the corresponding usage data for that account. You can select a child account from the table to view its cumulative usage data in the visual components.

To access this feature, navigate to Settings > Usage.

For more information, see Usage Reporting Overview in the product documentation.