v242 Release Notes

LogicMonitor now supports monitoring for AWS Connect as a first-class cloud resource, rather than a legacy instance. This enhancement enables auto-discovery, resource-level log mapping, and automatic ARN configuration for AWS Connect.

To access  this feature, navigate to Modules in LogicMonitor. Confirm that the AWS_Connect module is installed.

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

LogicMonitor now supports ARM64 (aarch64) architecture for Linux Collectors. You can now install, download, and manage Collectors on ARM-based Linux hosts, such as AWS Graviton and other aarch64 instances using the same Collector management workflows available for x64 Linux Collectors.

Key details include the following:

• Supported platform—Linux (arm64/aarch64)
• Minimum Collector version—EA Collector 40.500. Upcoming release. ARM64 supported Collectors will not be available for download until this release.
• Non-supported platforms—ARM64 Collector packages for Windows and other non-Linux platforms

You can now export Saved Views as JSON Query Packs and import them into the Log Query Library.
During import, LogicMonitor validates the uploaded file, creates new query groups as needed, and identifies naming conflicts before completing the import. These enhancements help you standardize and deploy reusable query libraries across users and environments.

To use the import functionality, navigate to Logs > Manage Saved Views > select Import saved views.

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

Log Files LogSources now support Dynamic Group Regex when used with LogicMonitor OpenTelemetry Collector 7.0.00 or later. This enhancement enables you to extract multiple metadata fields from a single log line using a single regular expression with multiple capture groups. You can reduce reduce configuration complexity and simplify maintenance for improving log parsing rules.

By eliminating the need to define multiple regular expressions for the same log format, RegexGroup simplifies LogSource configuration and makes complex log parsing rules easier to maintain.

To use this feature, navigate to Logs > LogSources, create or edit a Log Files LogSource, and add a Dynamic Group Regex mapping in the Log Fields section.

For more information, see Log Files LogSource Configuration and OpenTelemetry Collector Versions in the product documentation.

Log Query reports now support selecting custom metadata columns, generating reports in HTML and PDF formats, displaying Area, Column, Line, and Pie chart visualizations, and customizing the order of report sections.

These enhancements provide greater flexibility when configuring and sharing log reports.

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

You can now save and share complete Aggregate tab configurations with Saved Views. When you save a query, LogicMonitor preserves the selected visualization, grouping, aggregation logic, sorting, metric selection, time granularity (where applicable), and other supported display settings.

Exporting a Saved View as a Query Pack includes the Aggregate tab configuration, and importing the Query Pack restores the complete Saved View, making it easier to share and reuse curated queries and visualizations across environments.

You can now open the Query Library directly from the Logs homepage using the Open Query Library icon. The Query Library opens as an overlay panel that you can expand or collapse, providing faster access to your saved queries while maintaining the existing workflow.

This enhancement improves discoverability and reduces the number of steps required to access and manage Saved Views.

You can now create clearer and more informative visualizations in the Aggregate tab and Logs DB widgets. Column, Area, and Bar graphs now support properly rendered X-axis, improved Y-axis behavior, configurable labels and legends, and field aliases to display user-friendly names.

These enhancements improve readability, provide greater control over log-based visualizations, and ensure Logs DB widgets deliver a consistent experience with standard LogicMonitor dashboard widgets.

You can now control the display precision of Aggregate Big Number visualizations in the Aggregate tab and Logs DB widgets. Configure the number of decimal places to present metrics such as averages, error rates, and latency values in a cleaner, more readable format.

This enhancement improves dashboard readability, delivers consistent number formatting across log-based visualizations, and makes Big Number widgets better suited for operational and executive reporting.

The enhanced lm.data.topo and lm.data.topo.networking snippets add Nutanix signatures to support Nutanix Topology. Nutanix AHV MAC prefixes are classified as hypervisor, and Nutanix VM MAC prefixes are classified as virtual machine.

The enhanced Cisco Meraki NetScan now handles empty switch stack responses from the Meraki API without interrupting resource discovery. You can continue discovering other resources when switch stack enrichment returns no usable data instead of experiencing intermittent NetScan failures.

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

The enhanced Ruckus One AP NetScan now skips access points that have not yet contacted the Ruckus Cloud and do not return an IP address in the API response. This enables the NetScan to continue discovering other access points instead of failing when an access point returns a null networkStatus value.

For more information, see Ruckus One AP Monitoring in the product documentation.

The enhanced lm.data.topo snippet adds a Cisco wireless access point keyword rule to support addERI_Cisco PropertySource. You can now classify newer Cisco Meraki cloud-managed access points, such as the CW9172I, with an external resource type (ERT) of Wireless instead of Unknown.

In a future release, LogicMonitor Collectors will no longer support Apache Groovy 2. All official LogicMonitor-provided modules are compatible with Apache Groovy 4. To support this migration, LogicMonitor released 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 GD Collector 39.004 now uses Groovy 4 instead of Groovy 2.

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 7.0.00 expands OpenTelemetry support and improves data collection, performance, and stability.

This release includes the following enhancements:

• Added 25 new OpenTelemetry components, including 3 Connectors, 11 Processors, and 11 Receivers, expanding data collection, processing, and routing capabilities.

• Support for Dynamic Group Regex (RegexGroup) in Log Files LogSource. You can extract multiple metadata fields from a single log line using a single regular expression with multiple capture groups, simplifying LogSource configuration and improving log parsing efficiency.

• Updated the default hostmetrics filesystem scraper configuration to set include_virtual_filesystems: true by default. This enhancement improves filesystem metric collection in containerized environments and enables automatic attachment of modules such as LogicMonitor_APM_FileSystem for Docker-based deployments.

• Upgraded the embedded OpenTelemetry Collector and OpenTelemetry Collector Contrib to version 0.154.0 to provide the latest upstream features, performance improvements, and stability enhancements.

To use this feature, upgrade to LogicMonitor OpenTelemetry Collector 7.0.00.

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

As LogicMonitor continues to phase out the legacy UI, the New UI Preview switch will be removed from Resources (which includes Services), making Resources and Services 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, see Upcoming End-of-Life (EOL) for UIv3 Resources in LM Community.

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

In this release, LogicMonitor has made updates to REST API v3 Swagger, v3 Python SDK, and v3 GO SDK files.

New API Endpoints

The following table lists the new API endpoints:

Removed API Endpoints

The following table lists the removed API endpoints:

To bulk update log levels of all or multiple Collector components simultaneously, you can now use PUT /setting/collector/collectors/{id}/agentloglevels. This endpoint replaces PUT /setting/collector/collectors/{id}/agentloglevels/{component} which enabled you to update the log level of individual Collector components in a single API request.

These updates will be available after the LogicMonitor v242 production deployment is complete. For more information, see REST API Change Log and REST API v3 Swagger Documentation in the product documentation.

LogicMonitor plans to transition synthetic monitoring capabilities from LM APM Synthetics (SYN) to our new product, Synthetics and Internet Performance Monitoring, which provides enhanced visibility, broader monitoring capabilities, and a modernized platform architecture.

LM APM Synthetics is built on a legacy Selenium-based architecture, while our new product, Synthetics and Internet Performance Monitoring, provides globally hosted monitoring, advanced waterfall analysis, filmstrips and playback for transaction troubleshooting, and expanded test coverage across browser, API, network, and internet performance monitoring workflows.

There is no immediate change required, and you can continue using LM APM Synthetics during the transition period, until it is fully deprecated.

For more information about this transition, including roadmap details and evaluation guidance, see the Upcoming End of Life for LM APM Synthetics in LM Community.

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