v.246 Release Notes

You can now import GCP FOCUS Billing Exports into Cloud Operations Billing. This enhancement improves ingestion of GCP billing data by supporting data configured to FOCUS industry standards.

To access this feature, navigate to Cloud Operations > Billing and configure GCP billing to import cost and usage data.

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

Cloud Operations Billing now supports configuration and billing data for Oracle Cloud Infrastructure (OCI) billing. This enables you to view OCI billing data in your Billing dashboards, alongside info from other supported providers.

You must configure Billing to collect data from an OCI FOCUS report.

To access this feature, navigate to Cloud Operations > Billing.

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

You can now display metric data as a Heatmap visualization in the Advanced Metrics widget. Heatmaps group metric values over time and use color to show the concentration of values across time and value ranges, enabling you to identify patterns and variations in your metric data.

You can configure time buckets to control how data is grouped along the X axis and value range buckets to control how values are grouped along the Y axis. You can also configure the minimum and maximum values represented in the heatmap.

To access this feature, navigate to Dashboards, add or edit an Advanced Metrics widget, and select “Heatmap” from the Visualization Type dropdown menu.

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

The Advanced Metrics widget now supports OTLP queries using PromQL in addition to LMQL queries. You can select LMQL or OTLP as the query type when configuring the widget, enabling you to visualize both LogicMonitor metrics and OTLP metrics ingested through OpenTelemetry.

For OTLP queries, you can use Raw Query to enter a PromQL query directly. You can also use the Query Builder to build your query.

To access this feature, navigate to Dashboards, add or edit an Advanced Metrics widget, and select the query type.

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

You can now exclude Scheduled DownTime (SDT) periods at both the resource and resource group levels simultaneously when calculating SLA metrics in the SLA Widget.

Previously, you could exclude SDT periods at either the resource or resource group level, but not both. The combined option improves SLA calculation accuracy when individual resource maintenance overlaps with planned resource group maintenance.

You can now share Cloud Provider Health widgets directly from your LogicMonitor Dashboard. This enhancement creates a URL to access the widget, enabling you to share the widget with external users.

You must log in to the LogicMonitor portal to view the data in the dashboard widget.

To access this feature, navigate to Dashboards and select or create a Cloud Provider Health widget. Select Generate Link in the widget to create the URL.

For more information on sharing LogicMonitor dashboard widgets, see Widget Management in the product documentation.

You can now navigate directly from an alert on the Alerts page to its associated external ticket. Created external ticket IDs display as hyperlinks for ServiceNow, ConnectWise, Jira Service Management (JSM), Custom HTTP, PagerDuty, and Autotask integrations.

Each supported integration has its own external ticket column on the Alerts page. You can hide or unhide each column based on your environment and integration setup.

For Custom HTTP integrations, the configuration now includes an External ticket URL field. You can use this field to specify the integration portal URL for external ticket links. When configured, the external ticket ID for an alert displays as a hyperlink to the corresponding ticket in the external integration portal.

For more information, see Custom HTTP Delivery in the product documentation.

You can now sync resources with ConnectWise when a mapped value exceeds the supported ConnectWise character limit. Configuration sync automatically truncates the mapped value to the supported limit, and the truncated value appears in the ConnectWise configuration.

For more information, see ConnectWise Integration in product documentation.

The default value of the cisco.sdwan.maxDevicePages property is now 20, increased from three, to ensure all data is collected for larger environments.

The{{ rubrik.securitycloud }}snippet now supports Rubrik Security Cloud regional domain suffixes while preserving the default US endpoint.

Errors and unexpected HTTP responses now report as collection failures instead of producing empty discovery output. Previously discovered instances are retained when a collection failure occurs.

You can now set the optional redfish.ignore.proxy property to true to send Redfish requests that bypass the Collector proxy.

External resource type lookup now requires an exact sysOID match. A longer sysOID no longer matches a shorter prefix, which prevents some Huawei switches and wireless LAN controllers from being classified as routers.

Huawei resources are now mapped to the following resource types:

The Palo Alto Prisma SD-WAN Enhanced Script NetScan now uses the {{paloalto.prismasdwan }}snippet to select API versions during discovery, keeping onboarding aligned with the rest of the suite.

For more information, see Palo Alto Prisma SD-WAN Monitoring in the product documentation.

The veeam.vbr snippet now uses the REST API version detected on the resource by the addCategory_Veeam_VBR PropertySource when veeam.vbr.version is not set. An explicit veeam.vbr.version value overrides the detected version.

You can now use a manual paloalto.prisma.sdwan.region override for metric API calls. The paloalto.prismasdwan snippet also uses the wn_path filter for WAN-interface LQM queries and centralizes API version selection across Prisma SD-WAN modules.

You can now provide execution parameters when you manually run a DiagnosticSource from the Resource or Alert page to target a specific process or activity for diagnosis. The Execution Param tab on the Add DiagnosticSource page enables you to define parameters that override configured values in the script at run time. You must enable the Overriding Enabled option to override the default values. You can select text, number, or enum parameter types. Based on the selected type, you must provide parameter values for validation. When you run the DiagnosticSource, the Run Diagnostic dialog box enables you to specify values that override the configured values for targeted diagnosis. For example, if you have configured a generic script to provide information about network interfaces and their configuration on a Windows system, you can define execution parameters and provide specific values or instructions to control which network interface or configuration details the script retrieves or operates on. For subsequent runs, you can change the parameter values to perform a different task.

The ability to override configured values using execution parameters is available only when you manually run a DiagnosticSource from the Resource or Alert page. Automated executions from the Alert page run with the default values set in Execution Param.

In a Groovy or PowerShell diagnostics or remediation script, you can specify execution parameters and test whether the script is working as expected. To set execution parameters, your machine must have EA Collector 41.200 or later.

To access the Execution Param tab, navigate to Settings > LogicModules. In the Add modal, select DiagnosticSource.

For more information, see DiagnosticSource Configuration in the product documentation.

As of October 5, 2026, LogicMonitor no longer supports Apache Groovy 2 for LogicMonitor Collectors. Apache Groovy 4 replaces Apache Groovy 2, and all official LogicMonitor-provided modules are compatible with Apache Groovy 4.

For more information, see Apache Groovy 2 End-of-Life Milestone Public Announcement from the LogicMonitor Community documentation.

If your Collector upgrade was unsuccessful, resolve any outstanding issues and upgrade to MGD 39.005 or later to ensure your Collector runs a supported version.

For more information, MGD Collector 39.005 in the product documentation.

LogicMonitor now supports OpenTelemetry Metrics. You can send metrics from the OpenTelemetry Collector, LogicMonitor OpenTelemetry Collector, and other OpenTelemetry-compatible sources using the OpenTelemetry Protocol (OTLP) over HTTP/protobuf.

OpenTelemetry Metrics provides you with the following benefits:

• Centralized Metrics Monitoring—Monitor metrics from OpenTelemetry-compatible applications and infrastructure in LogicMonitor.
• Flexible Metrics Ingestion—Ingest metrics from multiple OpenTelemetry-compatible sources using OTLP over HTTP/protobuf.
• Metrics Querying and Visualization—Query, explore, and visualize ingested metrics using Metrics Explorer.
• Metric Alerting—Configure metric alert rules using Alert Configurations to monitor metric conditions.
• Dashboard Integration—Add metric visualizations to dashboards for improved visibility into application and infrastructure performance.

The OpenTelemetry Metrics feature must be enabled for your LogicMonitor portal, and you must have the applicable permissions. If you have any questions or require assistance, contact the Support team or your Customer Success Manager.

To access this feature, navigate to OTel Metrics in your LogicMonitor portal.

For more information, see OpenTelemetry Metrics Overview in the product documentation.

The Metrics Explorer report now supports OTLP queries using PromQL in addition to LMQL queries. You can select LMQL or OTLP as the query type when configuring a report, allowing you to report on both LogicMonitor metrics and OTLP metrics ingested through OpenTelemetry.

For OTLP queries, you can use the Raw Query option to enter a PromQL query directly. LMQL queries continue to support both the Query Builder and Raw Query options.

When using the API, you can set the queryType parameter to LMQL or OTLP. The default value is LMQL.

To access this feature, navigate to Reports, configure a Metrics Explorer report, and select the query type.

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

The Interfaces Bandwidth report now includes Inbound and Outbound Utilization (%) metrics as additional columns in the report output. These metrics help you understand how much of an interface’s available bandwidth is being used for inbound and outbound traffic directly from the report.

For supported non-CSV report formats, you can also view Inbound and Outbound Utilization graphs when graphs are enabled, providing a visual representation of interface utilization alongside the report data.

To access this feature, contact Customer Success.

For more information, see Interface Bandwidth Report in the product documentation.

When an Alert report is configured to include preexisting alerts, the report now combines active and cleared alerts from the configured time window, and active alerts from before the configured time window. This enhancement enables you to view relevant historical active alerts alongside alerts from your selected time window for a more comprehensive view of alert activity.

To access this feature, navigate to Reports > add an Alert report and configure the report to include preexisting alerts.

For more information, see Alerts Report in the product documentation.

You can now enforce Content Security Policy (CSP) for dashboard and widget content to control external content used by dashboard widgets. When you enable the CSP Allowlist, you can control the permitted external sources.

You can add and manage account-specific sources in the allowlist and enable only the sources required by your dashboard widgets. For new customers, by default, the dashboard CSP protection is enabled. For the existing customers ,Logicmonitor will communicate about enabling CSP for their portals.

To access this feature, navigate to Settings > Security.

For more information, see Security Settings in the product documentation.

LogicMonitor can now act as a SAML 2.0 identity provider (IdP),  enabling eligible LogicMonitor users to sign in to supported Service Providers (SPs) using Single Sign On (SSO). You can register a Service Provider by uploading its SAML metadata and then enabling the configuration.

You can also view and manage registered Service Providers and regenerate the certificate that LogicMonitor uses to sign SAML responses.

To use this feature, your LogicMonitor portal must have the Service Providers feature enabled. To add or modify Service Provider configurations, you need a LogicMonitor user with the applicable “Manage” permission for Single Sign On.

To access this feature, navigate to Settings > Single Sign On > Service Providers.

For more information, see Service Providers Overview 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.