v.238 Release Notes

You can now create shared filters to reuse filtering across multiple dashboards and users. You can keep views consistent across supported widgets and manage access with shared filter groups and role-based permissions.

Filters are available as the following types: private filters and shared filters. Private filters remain visible only to you and are now available across dashboards you can access. Shared filters are organized into shared filter groups and are accessible based on permissions. Existing private filters that were tied to a single dashboard are moved to a private folder named “Ungrouped,” where you can apply them across multiple dashboards.

You must have view access to shared filter groups to map filters. You must have manage access to shared filter groups to create, edit, or delete filters. You must have access to required resource and instance properties and dashboard permissions to apply and save filters.

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

The New UI Preview switch has been removed for 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 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.

You can measure application performance from an end-user perspective using synthetic web performance testing directly within the LogicMonitor platform.

Integrating Catchpoint Digital Experience into LogicMonitor includes the following benefits:

• End-to-end visibility—Monitors your application performance from infrastructure to real user experience.
• On-demand testing—Runs web performance tests instantly from within LogicMonitor.
• Faster troubleshooting—Correlates performance issues with alerts and monitored resources.

You can run tests for a specific resource or resource groups to check application performance and user impact. This self-service approach enables you to analyze issues during normal operations and incidents.

To access this feature, navigate to Digital Experience.
You can also initiate tests from Resource Explorer, Resource Tree, and Alerts by selecting a resource or alert and running a Digital Experience test.

For more information, see Enabling Digital Experience in LogicMonitor.

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

You can now configure the new Action Notes alert status on the integration pages for JSM, MS Teams, and Slack to update the Comments (for JSM) and messages (for MS Teams and Slack) with a DiagnosticSource output report in JSON or plain text format.

When a DiagnosticSource report is available for an alert, you can use the following tokens to configure the payload:

• ##DIAGNOSTIC_SOURCE_OUTPUT##
• ##DIAGNOSTIC_SOURCE_STATUS##
• ##MESSAGE##

These tokens apply only to the Action Notes alert status for the JSM, MS Teams, and Slack integrations.

For more information, see Jira Service Management Integration Setup, Integration for Slack, and Microsoft Teams Integration Setup in the product documentation.

You can now retain logs for up to two years, providing extended data availability for auditing, compliance, and historical analysis. This helps organizations meet regulatory standards (such as SOC 2, HIPAA, PCI-DSS and GDPR) while keeping log data accessible for historical reporting and evidence collection.

With extended retention, teams can maintain a centralized, searchable system of record for logs across their environment.

You must have an applicable log retention SKU to use this feature.

To access this feature, navigate to Logs > Partitions and configure the retention period for your partition.

You can now ensure more accurate log-to-resource mapping when using the OR resource mapping method. If multiple resources satisfy the condition, LogicMonitor does not associate the log with an ambiguous resource. Instead, the log is treated as a resourceless log.

This enhancement prevents incorrect mappings and maintains data integrity when multiple matches are found.

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

Enhanced cisco.meraki snippet now improves handling of 429 rate-limit responses to increase resilience during API throttling.

The enhanced proto.http snippet now supports the proxy.exclude property, enabling you to exclude specified traffic from proxy routing.

The enhanced Cisco Meraki NetScan now enables you to identify standby stack switches. When a standby switch shares an IP with an active switch, the system appends “.invalid” to the system.hostname.

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

The enhanced lm.remote snippet now supports the auto.ssh.preferredauthentications property. This improves flexibility when connecting to resources that require specific authentication methods.

The enhanced lm.data.topo snippet now identifies Juniper Ethernet Switch with Switch ERT.

The enhanced lm.topo snippet now enables you to set ERI through an overload method with hostProps support for added flexibility.

The enhanced vmware.vsphere.api snippet now authenticates the vSphere Automation REST API with improved compatible for vCenter 8.x appliance monitoring endpoints.

For more information, see VMware vSphere Monitoring in the product documentation.

The enhanced vmware.vsphere.sdk snippet enables you to process vCenter inventory faster with on-demand loading and a shared 15-minutes cache, which reduces repeated scans. You now experience more efficient folder traversal and improved stability during cluster host expansion with null-safe handling. These updates reduce vCenter load and help minimize timeouts in large or busy environments.

For more information, see VMware vSphere Monitoring in the product documentation.

The enhanced Cisco Catalyst Center NetScan now supports the discovery of resources that do not have a Site ID configured. This improves discovery coverage in environments where resources are not yet associated with a site.

You can also control whether credentials are automatically assigned to discovered resources. The new optional property, cisco.catalyst.credentials.addToAllDevices determines credential behavior. When the property is set to false, discovered resources are created without adding credentials. The default value is true, which adds credentials to discovered resources.

For more information, see Cisco Catalyst Center in the product documentation.

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

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:

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

You can now configure multiple weekdays within a single Weekly SDT recurrence using a shared start and end time. This enhancement eliminates the need to create separate SDT entries for each day and enables you to update selected days dynamically without recreating schedules.

This update improves efficiency when managing recurring maintenance windows across multiple days. It also supports single-day selection within the same configuration model, providing greater flexibility for scheduling.

To access this feature, navigate to Resource Tree > select a resource group > Schedule SDT.

For more information, see Resource SDT in product documentation.

Access to API v1 and v2 has been removed for new LogicMonitor accounts created after April 30, 2026. Existing accounts retain access and can continue current integrations without interruption. This change supports improved performance, enhanced security, and long-term scalability across the platform.

For more information about this removal, see Upcoming End of Life (EOL) for API v1 & v2 in LM Community.

For more information about the latest features and enhancements with LogicMonitor’s API, see REST API v3 Swagger Documentation in the product documentation.

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

Access to Websites is removed for environments that do not have access to the Websites product in Usage Reporting only. You can accomplish this same functionality using LM Uptime.

For more information about this removal, see Upcoming End of Sale (EOS) for “On-Demand” Legacy Websites (LWM) in LM Community.

For the most up-to-date information about how to continuously monitor websites, servers, and networking hardware from multiple locations, see LM Uptime 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.

In a future release, LogicMonitor will discontinue support for legacy LM Container builds and Argus versions 5, 6, 7, and 8. If you are running these versions, upgrade to a supported LM Container release to continue receiving updates and support.

The latest LM Container releases provide:

• Improved monitoring accuracy through updated and actively maintained code paths

• Latest security patches and compliance updates for modern Kubernetes environments

• Ongoing compatibility with newer Kubernetes versions and container runtimes