v227 Release Notes

LogicMonitor now monitors AWS resources located in the ca-west-1 and mx-central-1 AWS regions, and GCP resources located in the northamerica-south1 GCP region.

If your cloud resources are located in these regions, LogicMonitor automatically detects and begins monitoring them.

For more information, see Monitored Locations for Cloud Monitoring in the product documentation.

On the Collector page, for the ABCG Collector group, you can now view a new Calculated Threshold column. The values in this column indicate the threshold calculated for auto-scaling based on Collector size.

You can track how the threshold affects rebalancing decisions. For medium-sized Collectors, the default threshold is 10,000 instances, and the threshold limit is 15,000 instances.

For more information, see Auto-Balanced Collector Groups in the product documentation.

In LogicMonitor Dashboards, you can now create Billing Forecast widgets. This widget enables you to view projected costs for cloud resources monitored by Cost Optimization Billing directly on your Dashboards.

You must have access to Cost Optimization tools to access Billing Forecast widgets.

To configure a Billing Forecast widget, navigate to Dashboards and select Add Widget > Billing Forecast

For more information, see Billing Forecast Widget in the product documentation.

You can now configure Billing Widgets in LogicMonitor Dashboards to display Top Movers.

The Top Movers visualization enables you to compare the total cost of cloud resources over two specified time periods.

You must have access to Cost Optimization tools to access this widget.

To configure a new Top Movers widget, navigate to Dashboards and select Add Widget.

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

You can now choose an existing report group or create a new one when sharing a dashboard. Access to the shared dashboard is managed through users and roles, ensuring reports are only visible to the intended audience.

To access this feature, navigate to Dashboards > Select the dashboard you want to share > Manage Dashboard Options > Share Dashboard Report. Specify the name of an existing report group or a new report group when configuring the settings for sharing the dashboard.

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

You can now manage saved log queries more effectively with expanded options directly in the Manage Saved Filters panel. This improves reusability, organization, and tracking of your log queries across teams and environments.

Here are the newly added options in the Manage Saved Filters Panel:

• Rename: Update the name of a saved view to reflect new use cases or naming standards.
• Copy Link URL: Copy a shareable URL to the saved query for collaboration or support.
• Duplicate: Clone an existing saved view and assign it to another log query group.
• Track Query: Create a tracked query directly from a saved view.
• Move: Reassign a saved view to another query group for better organization.
• Export: Download the saved view definition as a JSON file for backups or migration.

For more information, see Logs Query Tracking in the product documentation.

LogicMonitor now leverages LM Uptime to continuously monitor websites, servers, and networking hardware from multiple locations. This ensures services remain responsive, reliable, and user-ready.

LM Uptime provides you with the following benefits:

• Easier Integration—Seamlessly add checks to resource groups, services, dashboards, and reports
• Property Inheritance—Automatically inherit properties just like other resources
• Resource Explorer Access—Manage your checks directly in Resource Explorer
• Resource Groups Access—Organize and manage checks using both static and dynamic groups

For more information, see LM Uptime Overview in the product documentation.

The updated lm.api snippet now supports multiple URLs. This enables greater flexibility and improves efficiency by reducing the need for separate configurations.

The following Enhanced Script NetScans for various platforms are now Groovy 4 compatible. For more information, see the product documentation:

• VMware vSphere Monitoring
• VMware SD-WAN Monitoring
• Versa SD-WAN Monitoring
• Aruba EdgeConnect SD-WAN
• Cisco Catalyst SD-WAN Monitoring
• Cisco Meraki Monitoring (Legacy)
• Cisco Meraki Monitoring
• Cisco Catalyst Center
• Juniper Mist Monitoring
• Palo Alto Prisma SD-WAN Monitoring

The lm.topo.data snippet now supports detection of Cisco Catalyst IE devices. This enhancement now enables more accurate topology mapping by automatically identifying Cisco Catalyst IE devices in your environment.

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

The cisco.catalyst.center snippet now supports caching for devices on each collector improving the performance of Catalyst Center modules.

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

The Cisco UCS X-Series NetScan now automatically applies the properties cisco.intersight.secret.key and/or cisco.intersight.secret.location to all onboarded devices by default. This enhancement now simplifies onboarding by ensuring required secret properties are consistently applied across Cisco UCS X-Series devices.

To override this behavior, set the property cisco.ucsx.key.addToAllDevices to false. When set to false, the NetScan does not add secret properties to onboarded devices.

For more information see, Cisco UCS-X Series Monitoring in the product documentation.

The lm.observer snippet now ensures the observer is rotated every 10 minutes. This enhancement improves accuracy by ensuring the observer does not remain stuck on a device with invalid credentials.

In a future release, LogicMonitor Collectors will no longer support Apache Groovy 2. All official LogicMonitor-provided modules will be compatible with Apache Groovy 4. To support this migration, LogicMonitor is releasing 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 LogicMonitor EA Collector 34.500 or later is compatible with Groovy 2 and Groovy 4. For more information about the EA Collector release, see the EA Collector 34.500 Release Notes.

The LogicMonitor EA Collectors 37.100, 37.200, and 37.300 which are now available, use Groovy 4 instead of Groovy 2. In accordance with Collector versioning, a stable EA version is designated as an optional general release (GD).

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

When running a module using Apache Groovy 4 with legacy classes in your script, the following exception can be thrown:

java.lang.RuntimeException: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed

To mitigate this issue, migrate to JPMS-compliant package names. Making this change does not break backward compatibility with Groovy 2.

For example, the following script uses legacy classes:

import groovy.util.XmlSlurper
import groovy.util.XmlParser
def xmlSlurper = new XmlSlurper()
def xmlParser = new XmlParser() 

You can replace the legacy classes with JPMS-compliant package names in Groovy 4 to resolve the exception, similar to the following:

import groovy.xml.XmlSlurper
import groovy.xml.XmlParser
def xmlSlurper = new XmlSlurper() 
def xmlParser = new XmlParser() 

You can now run Enhanced Script NetScans in Dry Run mode to validate device discovery without making changes to monitored resources. The system displays categorized device states and generates detailed discovery logs.

To access this feature, navigate to Settings > NetScans > All NetScans, select a NetScan configured with the Enhanced Discovery Method, and select Dry Run.

For more information, see Dry Run for Enhanced Script NetScan in the product documentation.

LogicMonitor has expanded reporting capabilities to include a new overall availability report for LM Uptime resources called the Uptime Resource Overview report. This report provides greater visibility into uptime performance by region, helping you identify localized issues, analyze response time trends, and share consistent reporting with stakeholders.

In addition, this new report type enables you to generate a report specifically for the LM Uptime resources and offers parity with the existing Website Overview report.

To access this feature, navigate to Reports > Add Report, and select Add for the Uptime Resource Overview report.

For more information, see Uptime Resource Overview Report.

You can now include “2FA Passkey” in a User report to identify which users have passkeys enabled for two-factor authentication (2FA). You can also use “2FA Passkey” as a filter when creating the report and configure the report to be sorted based on “2FA Passkey”, enabling you to focus on users based on their 2FA Passkey status. In generated reports, the 2FA Passkey displays as a dedicated column.

To access this feature, navigate to Reports > Add Report > User.

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

LogicMonitor now introduces Dynamic Service Insights (DSI), a next-generation capability that brings automation, flexibility, and scale for service monitoring. With DSI, you can automatically build and manage services using rules, ensuring service definitions stay synchronized with evolving infrastructure.

Dynamic Service Insights (DSI) provides you with the following capabilities:

• Automated Service Creation with Rules – Generate and update services dynamically based on property filters
• Flexible Naming & Grouping – Define patterns that reflect enterprise naming standards
• Instance-level Grouping – Organize services with finer granularity for precise insights
• Property Propagation & Contextualization – Carry resource attributes into services for richer context
• Service Availability – Derive availability KPIs using a new aggregation function Conditional Count

For more information, see Service Auto Creation Rules in the product documentation.

You can now view Edge Status in the Maps tab on the Resources and Alerts pages. This capability extends existing topology mapping functionality, enabling you to quickly assess connection health directly from more locations in the LogicMonitor portal.

To access this feature, navigate to the Resources or Alerts page, open the Maps tab, and review the Edge Status indicators.

For more information, see Maps Page in the product documentation.

In a future release of LogicMonitor, the support for LogicMonitor OpenTelemetry Collector 3.0.00 will be deprecated. Use the latest LogicMonitor OpenTelemetry Collector version.

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

LogicMonitor has now added a new Modules: Manage permission to Access Groups in the My Module Toolbox. This permission lets you fully manage modules mapped to their Access Group, including creating, cloning, deleting, and editing modules, including the AppliesTo field. Unlike the existing Manage (Limited) permission, the new permission provides full control, including the ability to create and delete modules.

In addition, Access Groups now supports tenancy. If an access group with tenancy is selected, the module auto-populates appliesTo with the tenant information (system.tenant.identifier property).

For more information, see Access Group Permissions and Tenant Identifier Property Name in the product documentation.