v.245 Release Notes

Alerts for deleted Websites erroneously display on the Alerts page when the filter for Include Deleted Resources/Website is configured to “No”.

You can now create a virtual group of Log Collectors to collect and process Syslog and SNMP Trap from resource, through LogSource applied to resource. The feature ensures that logs from the resource are processed consistently by any Collector (up to five) in the group. On the Collector page, the Log Collector tab has options to create and manage Log Collector Groups. A Collector can be part of a single Log Collector Group.

On the Resources page, the Set LM Log Collector Group switch enables you to set a Log Collector Group for the resource. You now have an alternative to collect and process Syslog and SNMP Trap logs using a single log Collector (the existing Set LM Log Collector switch) or a group of log Collectors (the new Set LM Log Collector Group switch).

To use this feature, you must be a LogicMonitor user with Manage permission for the resource, Collector, and Log Collector Group.

To access this feature, navigate to Settings > Collector. On the Log Collector tab, you can create and manage Log Collector Groups.

To set a Log Collector Group for a resource, navigate to Resource Tree > select a resource > Manage and toggle the Set LM Log Collector Group switch.

You can now install a LogicMonitor Collector and Catchpoint Enterprise Node on the same machine in a single installation session.

To install the Enterprise Node, you must do the following:

• Have a LogicMonitor user account with Catchpoint “Create & Modify” permissions for one or both of the Manage Enterprise Nodes And Machines For Client and Manage Enterprise Nodes And Machines For Division settings.
• Use EA Collector 41.100 or later to access this feature.

To access this feature, navigate to Collector > Add Collector, and toggle the Install Catchpoint enterprise node switch. If you do not see this option, contact your Customer Success Manager.

For more information, see Adding Collector in the product documentation.

You can now edit selected wildcard values for instance property filters without first deselecting the existing value. This enhancement reduces the typing needed to update a wildcard expression.

For more information, see Dashboard Filters in the product documentation.

To support dashboard performance, SLA widgets now use a maximum six-month time range. If you select a longer time range, the widget calculates the SLA using the most recent six months and displays the adjusted range in the header.

For more information, see SLA Widget in the product documentation.

You can now configure widget-level filtering in the SLA widget that operates independently of dashboard-level filters. You can filter by specific resources, instances, and properties to calculate and display SLA performance for a targeted subset of your infrastructure, such as a defined region, environment, or service.

Widget-level filters function separately from dashboard filters. You can apply broader dashboard filters or use drill-down actions without affecting the specific criteria configured for an individual SLA widget.

To access this feature, navigate to Dashboards and add an SLA widget.

For more information, see SLA Widget in the product documentation.

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 product documentation.

You can now access LogAlert actions directly from the Alert severity column on the Logs page.
The contextual menu provides the following benefits:

• View LogAlert details directly from the corresponding log entry.
• View the LogAlert configuration based on your role-based access control (RBAC) permissions.
• Update or delete a LogAlert from the Edit LogAlert Model modal based on your RBAC permissions.
• For stateful LogAlerts, view the alerting (start) and clearing (stop) conditions in a tooltip.

To access this enhancement, navigate to Logs and select the contextual menu in the Alert severity column.

You can now configure up to 30 LogAlert Groups per partition, increased from 20. In addition, each LogAlert Group now supports up to 40 configured LogAlerts.

For more information, see Considerations for LogAlert in the product documentation.

You can now monitor the health and performance of Citrix DaaS environments through the Citrix DaaS REST API. The package provides monitoring for delivery groups, machine catalogs, machines, applications, sessions, zones, licensing, and hypervisors.

The Citrix DaaS Monitoring package uses OAuth 2.0 client credentials for authentication.

You need the required Citrix Cloud credentials, service principal permissions, Collector connectivity, and LogicMonitor_Collector_Snippets DataSource.

To access this feature, navigate to the Module Exchange and install the Citrix DaaS monitoring package.

For more information, see Citrix DaaS Monitoring in the product documentation

The lm.remote snippet now gives resources up to five seconds to close the connection before the script terminates it automatically. This change can reduce open session counts on some resources.

The Module Snippet Loader now supports configurable cache access as an advanced diagnostic option. You can disable cache usage to use a disk-based fallback when diagnosing cache-related issues.

The Palo Alto Prisma SD-WAN NetScan now uses only the major Prisma SASE API endpoint versions that LogicMonitor supports. This change prevents the NetScan from automatically adopting a new major endpoint version that could introduce breaking changes to resource discovery.

Endpoint versions are now compared numerically, so version 2.10 is correctly recognized as newer than version 2.9.

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

You can now provide execution parameters when you manually run a RemediationSource from the Resource or Alert page to target a specific process or activity for remediation. The Execution Param tab on the Add RemediationSource 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 RemediationSource, the Run Remediation dialog box enables you to specify values that override the configured values for targeted remediation.

For example, if you have configured a generic script to perform disk cleanup operations on Windows systems, you can define execution parameters and provide specific values or instructions to remove only temporary files. 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 RemediationSource from the Resource or Alert page. Automated executions from the Alert page run with the default values set in Execution param.

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

For more information, see RemediationSource Configuration in the product documentation and Enterprise Node Overview from Catchpoint.

As of September 1, 2026, the required Minimum General Deployment (MGD) Collector 39.005 no longer supports Apache Groovy 2 and uses Groovy 4 instead. 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.

On October 5, 2026, LogicMonitor will enforce the upgrade for Collectors that have not been upgraded to the MGD Collector 39.005.

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.

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:

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]

// 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

You can now leverage a new filter in the Alert report and Alerts HealthCheck report to include or exclude alerts for deleted resources and websites. This provides you with greater control over historical alert data, enabling you to maintain historical audit trails, and use alert data for operational and compliance reporting.

To access this enhancement, navigate to Reports > create an Alert report or an Alerts HealthCheck report. The new filter is available in the Report Preview.

For more information about how to create these types of reports, see Alerts Report or Alert HealthCheck Report in the product documentation.

You can now include custom Resource and Instance properties in Standard (LMQL) Metrics Explorer reports so you can deliver client-ready reports that combine metric data with relevant resource metadata. This enhancement enables you to add business, customer, environment, location, or other contextual information to your metric analysis directly from LogicMonitor, reducing the need for manual post-processing and making reports easier to analyze and share.

The custom Resource and Instance properties display as custom columns alongside the metric data returned by your LMQL query in both report previews and generated reports. You can add properties through Column Settings and save your selected columns, column order, and visibility as part of the report configuration to support different reporting needs.

Custom property columns are supported for Standard (LMQL) Metrics Explorer reports only and are not available for OTLP reports.

To access this feature, navigate to Reports, and add a Metrics Explorer report.

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

Alerts for deleted Websites erroneously display in the Report Preview table of the Alert report when the filter for Include Deleted Resources/Website is configured to “No.”

The Traffic tab now retains applied filters when you change the global time range, enabling you to analyze NetFlow data across different time ranges without reapplying filters.

The Interfaces filter now displays the interface name and ID, and the Top Flows table displays interface names in the If In and If Out columns. If an interface name is unavailable, the interface ID displays instead. Filters reset to their default values when you navigate away from the Traffic tab.

Effective August 31, 2026, the legacy UI for Resources, including Services, has been removed. The New UI Preview switch has also been removed from Resources. Resources and Services are now available in the new UI only. The new UI provides an enhanced user experience, improved performance, and security features.

Use the new UI to access Resources and Services. Services now displays in the sidebar navigation.

For more information about this removal, see EOL for UIv3 Resources (including Services) is Complete! in LM Community.

For the most up-to-date information about the Resources and Services UI, see Navigating the Resources Page and Navigating the Services Insight Page in the product documentation.

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

Alerts fail to display for deleted resources or services on the Alerts tab at the Resource Group and Service Group levels when the filter is configured to include alerts for deleted resources.

LM APM Synthetics reached End of Sale on September 15, 2026. Existing customers can continue using LM APM Synthetics during the transition period, however, prior to their next renewal, they must transition to 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.