v.234 Release Notes

LogicMonitor now supports monitoring OCI Functions. This enhanced support enables you to monitor the health and performance of Functions within your OCI environments directly with LogicMonitor.

To monitor OCI resources, in LogicMonitor navigate to the Resource Tree and select Add > Cloud and SaaS > Oracle Cloud Infrastructure.

For more information, see OCI Monitoring Setup in product documentation.

LogicMonitor now supports monitoring OCI Site-to-Site VPN Service. This enhanced support enables you to monitor the health and performance of your site-to-site VPNs with LogicMonitor.

To monitor OCI resources, in LogicMonitor navigate to the Resource Tree and select Add > Cloud and SaaS > Oracle Cloud Infrastructure.

For more information, see OCI Monitoring Setup in product documentation.

Resource Explorer now displays the Cost tab when selecting the detail panel for groups of cloud resources. This enhancement enables you to view collective cost data for groups of related resources, and quickly access Cost Analysis for more details.

To access this feature, navigate to Resource Explorer > select a resource > Cost tab.

For more information on navigating Resource Explorer, see Resource Explorer Overview in product documentation.

Cost Optimization Recommendations now detects idle Azure Application Gateways, and recommends deleting unneeded app gateways.

This enables you to easily identify app gateways 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 leverage tokens that are available at the dashboard level directly in the Raw Query field of the Advanced Metrics widget. This enables you to reuse a single widget configuration across multiple resources or dashboard contexts by dynamically substituting values such as resource, group, or instance at runtime in the Advanced Metrics widget.

You must define the token at the dashboard level to enable token substitution in Raw Query.

To access this feature, navigate to Dashboards > add an Advanced Metrics widget or modify an existing one > Add a token to the Raw Query field.

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

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.

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 37.100, 37.200, 37.300, and 39.100 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).

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:

LogicMonitor OpenTelemetry Collector (lmotel) version 6.0.01 includes the following updates:

• Windows support—The lmotel collector can now be installed and run on Windows operating systems.
• Local log file ingestion on Windows—Supports ingestion of local log files on disk, enabling LogicMonitor Logs to capture operational data beyond Windows Event Logs. The supported use cases include the following:
• IIS logs—Monitor web server activity, response times, and errors
• Point-of-Sale (POS) system logs—Collect transactional and device-level data
• Custom application logs—Support for proprietary formats and business-critical logs
• Audit and transaction logs—Enhance compliance, troubleshooting, and root cause analysis
• Local log file ingestion on Windows—Supports ingestion of local log files on disk, enabling LM Logs to capture operational data beyond Windows Event Logs. 
  For configuration details, see Log Files LogSource Configuration in product documentation.
• Improved security defaults for OTLP receiver—Protect the lmotel collector from denial-of-service (DoS) attacks, the default configuration for the otlpreceiver has been updated to listen on localhost instead of 0.0.0.0.
  In environments with non-standard networking setups (for example, Docker or Kubernetes), localhost may not function as expected.
  For more information on best practices, see Protect against denial-of-service attacks from OpenTelemetry.
• Enhanced log filtering capabilities—Added support for AND or OR operators, along with Include and Exclude filter types in Log Files LogSource filters.
• PII obfuscation in the collector pipeline—Added logic to obfuscate Personally Identifiable Information (PII) using predefined regular expressions. Fields such as email addresses, IPs, and user identifiers are masked before export.
• Removed logging exporter—The logging exporter has been removed and replaced with the debug exporter.

For more information, see OpenTelemetry Collector Versions in the product documentation. 

Support for LMOtel Collector version 6.0.00 has been removed due to operational behavior changes. Upgrade to 6.0.01 to ensure continued and uninterrupted service.

For more information on supported versions, see OpenTelemetry Collector Versions.

You can now control how results display in Log Query Reports by choosing to display raw log events, aggregated results, or both in the same report. This enhancement expands existing Log Query Report functionality so you can tailor reports for detailed investigations, trend analysis, or combined views that provide context alongside summarized insights. You can display individual log messages for audits and troubleshooting, aggregated summaries for high-level reporting, or a combined view that presents detailed events together with grouped results.

To access this feature, navigate to Reports, and add a Logs Query report.

For more information, see Log Query Report in the product documentation.

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

The custom host properties display as custom columns alongside resource metrics such as instance, datapoint, and resource in exported reports. You can save custom column selections as reusable report templates to support different reporting needs.

To access this feature, navigate to Reports, and add a Resource Metric Trends report.

For more information, see Resource Metrics Trends Report in the product documentation.

Metrics Explorer report fails to display data for the following complex LMQL queries:

• TopK Query used with comparison operator along with arithmetic operation
  For example:

  topk(1, Percent_used{system.displayname="LMI_DEVICE_DO_NOT_DELETE"} > 80) != 92

• Sum of aggregate queries with different instant vector queries
  For example:

  avg(Percent_used{system.displayname="LMI_DEVICE_SECOND_DO_NOT_DELETE",datasource="AVS_SSH_Filesystems_DND",instance=~"dev.*"})
  + max(Percent_used{system.displayname="LMI_DEVICE_DO_NOT_DELETE",datasource="AVS_SSH_Filesystems_DND",instance=~"dev.*"})
  + min(Percent_used{system.displayname="LMI_DEVICE_DO_NOT_DELETE",datasource="AVS_SSH_Filesystems_DND",instance=~"dev.*"})

• Instant Vector Queries sum with literals
  For example:

  Percent_used{system.displayname="LMI_DEVICE_DO_NOT_DELETE"} + 10

• Aggregate queries with replace function
  For example:

  avg(topk(3, (replace(Percent_used{system.displayname="LMI_DEVICE_DO_NOT_DELETE"}, 98, 198))))

• Arithmetic operations between different topk and bottomk queries
  For example:

  topk(3, Percent_used{system.displayname="LMI_DEVICE_SECOND_DO_NOT_DELETE",datasource="AVS_SSH_Filesystems_DND",instance=~"dev/.*"})
  /
  bottomk(3, Percent_used{system.displayname="LMI_DEVICE_SECOND_DO_NOT_DELETE",datasource="AVS_SSH_Filesystems_DND",instance=~"dev/.*"})

LogicMonitor now supports Component Auto Discovery, enabling service components to be dynamically derived from device and instance properties. This removes the need for static component definitions and improves support for highly dynamic service architectures.

Service component DataSources can automatically discover and manage components based on property values across service members. As property values are displayed, changed, or removed, component instances are created, recovered, or removed accordingly.

This enhancement includes the following capabilities:

• Property-driven component discovery from service member devices or instances

• Configurable deletion behavior, including immediate deletion or delayed cleanup after a retention period

• Soft delete and recovery support to preserve component identity and historical data when properties fluctuate

• DataSource-driven discovery scheduling for controlled and predictable execution

These enhancements automatically migrate existing static service component DataSources to  dynamic property-driven component datasources.

For more information, see Aggregate Data Collection Method 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 provides the following benefits:

• Improved monitoring accuracy using 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 details and further removal updates, 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.