v.247 Release Notes

In a future release of LogicMonitor, the ability to monitor billing data from cloud resources using DataSources will be removed. You can accomplish this same functionality using the Cost Optimization Billing features of Cloud Operations.

To access this feature, you must purchase Cost Optimization tools.

For more information about this deprecation, including timeline and further updates about the removal, see End of Life (EOL) for Legacy Cloud Billing DataSources in LM Community.

For more information, see Cloud Operations Billing Overview in the product documentation.

You can now securely visualize OpenTelemetry (OTel) metrics in Advanced Metrics dashboard widgets using scope-based access control. This enhancement ensures that you see only the metrics associated with your permitted scopes, helping maintain data isolation across environments and teams.

With Attribute-Based Access Control (ABAC), the Advanced Metrics widget automatically filters OTel metrics based on the configured Metrics Scope and your assigned permissions. This helps prevent unauthorized access to metrics while enabling teams to use shared dashboards without exposing data from other environments.

Existing widgets without a configured scope continue to display metrics based on your permitted scopes. Widgets with a configured scope display only data you are authorized to access.

To access this feature, navigate to Dashboards > create or edit an Advanced Metrics widget.

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

You can now configure Advanced Metrics widgets with a predefined or custom time range. Select a predefined range, such as Last 2 hours, to display data for a rolling time window, or specify a custom start and end date and time to display data for a fixed period.

Custom time ranges support your configured time zone and remain intact when you save, edit, clone, or export and import widgets and dashboards. Widgets using the default time range continue to follow the dashboard time range.

To access this feature, navigate to Dashboards, configure the Advanced Metrics widget, and use the time picker dropdown to select Predefined or Custom.

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

You can now import saved LM Logs queries into the query library from the Module Toolbox. Imported queries can be added to the Private, Shared, or Public section of the query library, with existing access permissions applied to the destination section. During import, LogicMonitor detects duplicate queries and query name conflicts, creates new query groups when needed, and renames conflicting queries.

To access this enhancement, navigate to Logs > Views > Manage Saved Views, and select an import option from the Import dropdown menu.

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

You can now configure resource mappings for Log Files LogSources to associate ingested logs with monitored resources. Resource mappings support AND and OR operators and multiple mapping methods to identify the appropriate resource.

You must use LM OTel Collector version 7.1.0.0 or later to configure resource mappings for Log Files LogSources.

To access this feature, navigate to Modules > My Module Toolbox, add or edit a Log Files LogSource, and configure the Resource Mappings section.

For more information, see Log Files LogSource Configuration in the product documentation.

You can now manage LogAlert Groups and LogAlerts from the consolidated LogAlert Groups & LogAlerts page in Logs Management.

The new management experience enables you to view, filter, add, edit, and delete LogAlert Groups and LogAlerts without navigating to separate management pages. You can also expand rows to view additional information and use the Preview/Logs and History options when viewing or editing LogAlerts to review LogAlert results and modification history.

To access this feature, navigate to Logs > More Options > Logs Management > LogAlert Groups & LogAlerts.

For more information, see LogAlert Groups and LogAlerts Management in the product documentation.

LogPatterns now provide parameterized values for variable portions of a pattern. You can select an emphasized <*> placeholder to view the top 10 most frequently occurring values and the bottom 10 least frequently occurring values for that parameter. This helps you identify the values that occur most or least frequently in logs matching the pattern and investigate variations within the pattern.

LogPatterns also display the first and last occurrence timestamps of logs that contributed to a particular pattern, helping you determine when the pattern occurred during the selected time range.

For more information, see LogPatterns Results and LogPatterns in LogicMonitor in the product documentation.

LM Logs now supports querying multiple log partitions across supported Logs features. You can search up to five partitions in a single query and use multiple partitions with Saved Views, LogAlerts, dashboard Log Query widgets, Log Query Reports, tracked queries, and resource logs.

Partition permissions determine which partitioned log data you can access across these features. If you have access to only some of the configured partitions, you can access log data only from the permitted partitions. Access to an LM Logs object does not provide access to restricted partition data.

Existing single-partition configurations and workflows continue to function.

To configure partition permissions, navigate to Settings > Users and Roles > Roles, add or edit a role, and configure the applicable Partitions permissions from Logs & Traces.

For more information, see Log Partitions and Logs & Traces Role Permissions in the product documentation.

LogicMonitor now supports Log Query Pack, a new LogicModule type that enables you to group multiple saved log queries into a single, reusable module.

Log Query Packs provide the following benefits:

• Simplified Query Management—Organize multiple saved log queries into a single, reusable module
• Query Reusability—Reuse predefined log queries without creating them individually
• Access Control—Assign access groups to manage access to Log Query Packs
• Query Validation—Validate log queries before adding them to a pack

To access Log Query Packs, navigate to Modules > My Module Toolbox, where you can create and manage packs, configure access groups, and add validated log queries.

For more information, see Log Query Pack Overview.

Removed an extra slash from the netapp.restclient snippet that caused // in URLs. This change has no customer impact because the NetApp REST API ignores // in URLs.

Improved the Cisco Catalyst SD-WAN Enhanced Script NetScan now uses the latest version of the cisco.sdwan snippet to resolve vManage authentication failures (HTTP 403 and 405 errors) caused by stale session cookies and cached tokens.

The NetScan also provides a clear error message when it cannot retrieve devices from the vManage API.

For more information, see Cisco Catalyst SD-WAN Monitoring in the product documentation.

Fixed an issue where Cisco SD-WAN (vManage) authentication could fail with HTTP 403 or 405 errors when the collector JVM held a stale session cookie for the vManage host.

The cisco.sdwan snippet now clears stale cookies before login, retrieves the new session cookie reliably, and requests a fresh XSRF token after each new login.

The lm.remote snippet now supports ssh.key and ssh.privatekey properties to specify the SSH private key location, and ssh.key.pass and ssh.privatekey.pass properties to specify the key passphrase. Although SSH uses public key authentication, the ssh.privatekey property more clearly identifies the private key location required for authentication. The existing ssh.cert and ssh.publickey properties continue to work.

The lm.data.topo snippet no longer creates invalid topology resources for FortiGate dial-up phase 1 configurations that do not report a local gateway. The placeholder identifier endpoint:fortigate–0.0.0.0– is excluded so it does not create an invalid topology resource. Revised to avoid assuming Router ERT when ‘/switch’ appears in system.sysinfo.

LogicMonitor OpenTelemetry Collector 7.1.00 now supports exporting OpenTelemetry Metrics and includes configuration polling and resource mapping enhancements.

This release includes the following enhancements:

• LogicMonitor OpenTelemetry Metrics Exporter—Added the lmotelexporter custom exporter for exporting OpenTelemetry metrics.

• LogSource Resource Mapping—For SCRAPE_LOGS, you can now configure _lm.resourceId for individual LogSources using CloudHost, DisplayName, LmOtelHost, Token, Static, Regex, and RegexGroup feed methods with AND/OR operations. Empty mapping values are skipped. Older Collectors continue to use the existing global resource mapping behavior.

To use these enhancements, you must upgrade to LogicMonitor OpenTelemetry Collector 7.1.00.

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

You can now use OpenTelemetry Metrics scopes to control access to metrics based on OpenTelemetry metric attributes and values. The new Scopes tab enables you to organize scopes into a hierarchy and manage scope access through role permissions. You can also create, clone, edit, and delete scopes based on your permissions.

To access this feature, navigate to More > OTel Metrics > Scopes.

For more information, see Scopes Overview in the product documentation.

You can now securely visualize OpenTelemetry (OTel) metrics in the Metrics Explorer report using scope-based access control. This enhancement ensures that you see only the metrics associated with your permitted scopes, helping maintain data isolation across environments and teams.

With Attribute-Based Access Control (ABAC), the Metrics Explorer report automatically filters OTel metrics based on the configured Metrics Scope and your assigned permissions. This helps prevent unauthorized access to metrics while enabling teams to use shared dashboards without exposing data from other environments.

Existing reports without a configured scope continue to display metrics based on your permitted scopes. Reports with a configured scope display only data you are authorized to access.

To access this feature, navigate to Reports > create or edit a Metrics Explorer report.

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

You can now add multiple metric queries to a Metrics Explorer report, enabling you to compare and visualize related metric data within the same report.

You can also apply transformations to reshape and organize results from multiple queries. Supported transformations include Merge, Series to Rows, Organize Fields, and Sort, giving you greater control over how query results are combined and displayed.

To access this feature, navigate to Reports, add or edit a Metrics Explorer report, and configure multiple queries.

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

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

The following table lists the new API endpoints:

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

You can now access associated LogicMonitor portals from a central portal using Single Sign On (SSO), simplifying navigation between your related LogicMonitor portals without requiring you to enter your credentials again.

The portal switcher lists the associated portals available from the central portal. When you select an associated portal, LogicMonitor opens the portal in a new browser tab and authenticates you using SSO.

The Multiportal feature must be enabled for the applicable LogicMonitor portals, and SSO must be configured between the central portal and associated portals.

To access an associated portal, select the current portal name in the central LogicMonitor portal, and then select the associated portal from Other portals.

For more information, see Multiportal Overview in the product documentation.

LogicMonitor is upgrading the Microsoft JDBC Driver for SQL Server from 7.4.1.jre11 to 13.4.0.jre11, which is included with the LogicMonitor Collector, to address a security vulnerability. The update is planned for EA Collector 41.300 on 12/02/2026 and is expected to move to the General Deployment (GD) Collector release track in February 2027, subject to release scheduling.

The updated driver enables encryption by default when the encrypt setting is not explicitly defined in the SQL Server connection string. Server connection string. Existing automatically discovered or manually configured SQL Server connection URLs might require updates to prevent monitoring interruptions.

Before upgrading, review the mssql.<instance>.mssql_url and auto.<instance>.mssql_url properties and explicitly configure the appropriate encryption and certificate trust settings. Connections that use untrusted, expired, or mismatched certificates can fail when certificate validation applies.

Connections configured with encrypt=false can also encounter certificate validation failures if SQL Server is configured to force encryption. LogicMonitor recommends using encrypted connections with valid, trusted certificates. Test applicable SQL Server monitoring connections with EA Collector 41.300 beginning 12/02/2026 and resolve identified configuration issues before upgrading to the anticipated GD Collector release track in February 2027.

You can now configure metric thresholds directly when you create a service, instead of adding them separately after service creation.

After adding resources or instances as service members and selecting their metrics, you can define thresholds for different alert severity levels. You can configure infrastructure health monitoring as part of the initial service setup.

For more information, see Service Addition in the product documentation.

Service Insights now integrates with Digital Experience, so you can associate synthetic tests with your services and monitor infrastructure and digital experience health together.

When creating or managing a service, you can automatically discover Digital Experience tests using service member properties or manually search using URLs, IP addresses, ASNs, labels, test names, or test IDs. You can select which tests and metrics contribute to service health, and the test associations automatically update as the discovery criteria change.

The Service Insights Status page now displays separate Infrastructure, Digital Experience, and Overall Service Status, along with associated Experience Test datapoints and alerts.

This feature is available with the purchase of Digital Experience.

For more information, see Service Addition in the product documentation.

LogicMonitor plans to transition synthetic monitoring capabilities from LM APM Synthetics (SYN) to Catchpoint 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, and Catchpoint represents the long-term direction for synthetic monitoring within the LogicMonitor platform. Catchpoint 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.

Fixed an issue that could cause incorrect connection information to display when Edge Status was enabled on a topology map with unsaved changes. The Edge Status toggle remains disabled until the newly created map is saved.

You can now view distributed traces associated with web-based Digital Experience Synthetic Tests that have tracing enabled in your LogicMonitor portal. The End-to-End Trace View provides detailed trace information associated with the synthetic test record.

When you access a trace from a Digital Experience Synthetic test record, select Back to test record to return to the originating record.

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