v.244 Release Notes

You can now include percentile_over_time:N rollups in the aggr_over_time function in LogicMonitor Query Language (LMQL), alongside existing rollups such as avg_over_time, max_over_time, and sum_over_time. This enhancement provides greater flexibility when querying and reporting percentile values with other over-time aggregations.

You can specify an integer percentile value from 0 through 100, such as percentile_over_time:95 or percentile_over_time:40. When you specify multiple rollups, the API returns a separate result for each rollup and matching instance or datapoint. The Function field identifies the rollup associated with each result, including individual percentile values.

To access this functionality, navigate to Dashboards > create an Advanced Metrics widget. Use percentile_over_time:N in the aggr_over_time function in the Query Builder. Alternatively, you can manually enter the queries using raw query.

For more information, see LogicMonitor Query Language (LMQL) Reference in the product documentation.

You can now refresh applicable widgets on the current dashboard on demand without performing a full browser refresh. The Refresh icon displays next to Dashboard Time and refreshes the dashboard widgets with the latest data while preserving your current dashboard context.

You can now use an OK alert status in the NOC widget configuration. This setting is enabled by default.

When you disable the toggle, the widget excludes healthy resources and displays resources that match the remaining enabled statuses.

You can now display Cloud Provider Health Events as a timeline visualization within the Cloud Provider Health Widget. You can display timeline data using vertical or horizontal options. This enhancement provides context to cloud health events, enabling you identify trends and potential downstream issues in your cloud environments.

For more information, see Cloud Provider Health Event Widgets in the product documentation.

You can now monitor Microsoft Internet Information Services (IIS) access logs by using the OpenTelemetry (OTel) Collector. The IIS Server Logs LogSource simplifies IIS log onboarding by automatically collecting and parsing IIS access logs into structured metadata for querying, alerting, and dashboarding. It supports standard IIS log locations and extracts commonly used IIS fields to accelerate troubleshooting and operational visibility.

You must use the OpenTelemetry (OTel) Collector for Windows version 7.0.00 or later.

To access this feature, navigate to Logs > Modules > Exchange and add the IIS Server Logs LogSource.

You can now associate a tracked query with an existing LogicMonitor resource when tracking a query. This enhancement enables tracked query instances to be created under the selected resource instead of a default resource, providing better visibility and easier navigation from the associated resource.

To access this feature, navigate to Logs > Manage Saved Views, select a saved query, and then select Track query.

For more information, see Log Query Tracking and Tracked Query Management in the product documentation.

You can now define Syslog and SNMP Trap LogSource filters by using a single free-text complex filter query instead of configuring legacy filters one row at a time. Complex filters support multiple filter predicates combined with AND, OR, and parentheses, enabling you to create more flexible and expressive filtering logic. Only log messages or SNMP traps that match the configured complex filter are ingested.

The enhanced paloalto.prismasdwan snippet improves collection reliability when the Prisma SD-WAN API reaches its rate limit. The snippet now retries rate-limited requests using exponential backoff and honors the Retry-After response header.

The snippet also reduces API requests by caching configuration responses and access tokens by tenant service group. It excludes inactive, disconnected, or unassigned elements from metric collection and removes literal “null” values from topology External Resource IDs (ERIs).

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

The enhanced lm.data.topo snippet improves external resource type (ERT) assignment when generating topology data. Linux resources are more accurately matched to the PhysicalServer ERT, Sophos XG firewalls are matched to the Firewall ERT, and ArubaCX Switches receive improved ERT assignment.

In addition, the Cisco ASA matching pattern is more specific. Linux resources with “ASA” in their system information are correctly classified, reducing incorrectly classified resources in your topology maps.

The enhanced Cisco UCS-X NetScan now assigns the cisco.intersight.serial property to all discovered chassis, server, and fabric interconnect resources. You can use this consistent property to identify and filter Cisco UCS-X resources during onboarding.

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

The Fortinet_FortiGate_HighAvailabilityPeers module is deprecated and replaced by Fortinet_FortiGate_HAPeers. The new module adds support for filtering standalone resources to prevent duplicate alerts and unnecessary instance creation.

You can retain historical data and use standalone-resource filtering by disabling monitoring for the existing Fortinet_FortiGate_HighAvailabilityPeers module and importing the Fortinet_FortiGate_HAPeers module.

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.

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

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

def numbers = [1, 2, 3, 4]
println numbers.remove(numbers.size() - 1) 
// OUTPUT: 4

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

You can now include percentile_over_time:N rollups in the aggr_over_time function in LogicMonitor Query Language (LMQL), alongside existing rollups such as avg_over_time, max_over_time, and sum_over_time. This enhancement provides greater flexibility when querying and reporting percentile values with other over-time aggregations.

You can specify an integer percentile value from 0 through 100, such as percentile_over_time:95 or percentile_over_time:40. When you specify multiple rollups, the API returns a separate result for each rollup and matching instance or datapoint. The Function field identifies the rollup associated with each result, including individual percentile values.

As LogicMonitor continues to phase out the legacy UI, the New UI Preview switch will be removed from Resources (which includes Services), making Resources and Services 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.

LogicMonitor plans to transition synthetic monitoring capabilities from LM APM Synthetics (SYN) to our new product, 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.

There is no immediate change required, and you can continue using LM APM Synthetics during the transition period, until it is fully deprecated.

As of July 31, 2026, LogicMonitor has removed support for legacy LM Container builds and Argus versions 5, 6, 7, and 8. These versions no longer receive updates or support.

You must upgrade to a supported LM Container release to receive current security and compliance updates, maintain compatibility with newer Kubernetes versions and container runtimes, and use actively maintained monitoring functionality.

For LM Container installations running Argus version 8, use the LM Upgrade Wizard or CLI to upgrade.

For more information about the removal, including timeline and further updates about the removal, see End-of-Life (EOL) for Legacy Versions 5, 6, 7, and 8 for LM Container & Argus is Complete in the LM Community.

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