v.232 Release Notes

Cost Optimization Recommendations now detects idle AWS Load Balancers, and recommends deleting unneeded load balancers.

This enables you to easily identify load balancers that are inactive, and provides potential savings estimates from deleting those resources.

For more information, see Cost Optimization – Recommendations in the product documentation.

You can identify the highest- or lowest-performing metric time series by using the topk() and bottomk() functions. You can surface the most important datapoints for dashboards, anomaly detection, performance analysis, and visual comparisons. You can improve query precision by chaining aggregations and applying these functions across dashboards and reports.

You can apply these functions for use cases such as identifying top interfaces by bandwidth usage, servers by memory consumption, websites by latency, or hosts, interfaces, and services with the lowest values in their respective categories. These functions can operate over full time series and support chained aggregations.

To access this feature, navigate to the locations where LMQL queries are supported in LogicMonitor (such as the Advanced Metrics widget in Dashboards or the Metrics Explorer report in Reports).

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

You can now use a table visualization in the Advanced Metrics widget. This enhancement enables you to compare datapoint values returned by LMQL queries in a structured table similar to the existing Table widget. You can more effectively analyze aggregated metrics across multiple resources and identify performance patterns or anomalies.

To access this feature, navigate to Dashboards and create a new Advanced Metrics widget or edit an existing one. In the widget configuration, select “Table” as the type of visualization for the data.

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

You can now perform various actions on a Table widget that is added to a Dashboard. This provides you with more flexible actions when interacting with widgets, enabling you to engage in active troubleshooting more efficiently. For example, you can select a property in a table and navigate directly to the corresponding Resources in the Resource Tree to view the data for that instance.

To access this feature, navigate to Dashboards, and add a Table widget to the Dashboard. Select a property in a table to display the options for the actions.

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

You can now monitor Nutanix Prism Central environments with out-of-the-box LogicModules. These modules give you visibility into clusters, AHV hosts, virtual machines, and overall platform health.

This monitoring uses the Nutanix Prism Central v4 REST APIs and begins collecting data after you install the required LogicModules and onboard resources.

To access this feature, navigate to Modules > Exchange and install the Nutanix Prism Central monitoring package.

For more information, see Nutanix Prism Central Monitoring in the product documentation.

The enhanced VMware vSphere NetScan now improves display name deduplication and emits a serial number value for additional deduplication validation.

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

The enhanced cisco.dnac snippet now constructs paginated API requests correctly for the Cisco DNA Center integration. Pagination parameters concatenate using “&” when a query string is already present, which prevents HTTP 404 errors. You can collect data without interruption when pagination is required.

For alerts, you can now replace numeric status data point values with readable status names. This improves alert readability and helps you understand status conditions without interpreting raw numbers.

Some data points report numeric values that represent a status rather than a measurement. Status Display Names enable you to map those values to descriptive text, such as mapping a value of 3 to Non-operational. LogicMonitor displays the mapped status name in alerts by using new alert tokens, instead of showing the numeric value. This feature supports all metric types and both normal and complex data points.

LogicMonitor intends to incrementally update the status display names of official DataSources.

To access this feature, navigate to Modules > select an existing DataSource or add a new one > open or add a datapoint, then select Add Status Display Name.

For more information, see Normal Datapoints and Complex Datapoints in the product documentation.

Fixed an issue in the Cisco UCS-X Series NetScan that caused the system category output to be incorrect. You can now see accurate system category information when running NetScan.

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

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

Fixed an issue that caused data collection failures when the Cisco DNAC integration generated paginated API requests. The EventSource added a “?” to URLs that already contained query strings, which produced HTTP 404 errors.

URLs now concatenate pagination parameters with “&” so you can collect data without interruption.

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

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()

LogicMonitor OpenTelemetry Collector (lmotel) version 6.0.00 includes the following updates:

• Windows support—The lmotel collector can now be installed and run on Windows operating systems.

• Local log file ingestion on Windows—Supports ingestion of local log files on disk, enabling LogicMonitor Logs to capture operational data beyond Windows Event Logs. The supported use cases include the following:
  • IIS logs—Monitor web server activity, response times, and errors
  • Point-of-Sale (POS) system logs—Collect transactional and device-level data
  • Custom application logs—Support for proprietary formats and business-critical logs
  • Audit and transaction logs—Enhance compliance, troubleshooting, and root cause analysis
  • Local log file ingestion on Windows—Supports ingestion of local log files on disk, enabling LM Logs to capture operational data beyond Windows Event Logs.
    For configuration details, see Log Files LogSource Configuration in product documentation.

• Improved security defaults for OTLP receiver—Protect the lmotel collector from denial-of-service (DoS) attacks, the default configuration for the otlpreceiver has been updated to listen on localhost instead of 0.0.0.0.
  In environments with non-standard networking setups (for example, Docker or Kubernetes), localhost may not function as expected.
  For more information on best practices, see Protect against denial-of-service attacks from OpenTelemetry.

• Enhanced log filtering capabilities—Added support for AND or OR operators, along with Include and Exclude filter types in Log Files LogSource filters.

• PII obfuscation in the collector pipeline—Added logic to obfuscate Personally Identifiable Information (PII) using predefined regular expressions. Fields such as email addresses, IPs, and user identifiers are masked before export.

• Removed logging exporter—The logging exporter has been removed and replaced with the debug exporter.

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

The support for LogicMonitor OpenTelemetry Collector 3.0.00 has now been removed. Use the latest LogicMonitor OpenTelemetry Collector version.

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

You can now add a Metrics Explorer report–a new report type that enables you to query an aggregation of metrics across multiple DataSources. This enhancement enables you to effectively highlight the data most relevant to identifying root causes, prioritizing alerts, and reducing time to resolution.

The Metrics Explorer report leverages the LogicMonitor Query Language (LMQL) to extend LogicMonitor’s platform giving you greater control and flexibility in how you query and filter your data. LMQL uses a query-based approach to analyze large data sets, customize visualizations, and extract meaningful insights.

To access this feature, navigate to Reports > select Add for the Metrics Explorer report.

For more information, see Metrics Explorer Report and LogicMonitor Query Language (LMQL) Reference in the product documentation

LogicMonitor has updated LogicMonitor REST API v3 Swagger, v3 Python and v3 GO SDK files with the following new API endpoints:

These updates will be available after LogicMonitor v232 deployment to production is complete. For more information, see REST API Change Log and REST API v3 Swagger Documentation.

Fixed an issue that enabled users with an out-of-the-box Administrator role to make GET /setting/collector/collectors/{collectorId}/installers/{osAndArch} requests using API tokens. After applying the fix, users with an out-of-the-box Administrator role cannot make LogicMonitor REST API requests.

SAML-based Single Sign-On (SSO) users can now self-activate their accounts when suspended due to inactivity. When a user attempts to log in after their account has been suspended, a secure recovery link is sent to their registered email address. This enhancement streamlines access recovery, reduces support overhead, and improves the overall user experience for organizations using SAML authentication for SSO.

For more information, see Admin Account Recovery for Inactivity Suspension in the product documentation.

You can now configure inactive session timeouts at the user level, providing greater flexibility and control over session security. When a timeout value is set at the user level, it overrides the timeout value configured at the portal level.

For more information, see LogicMonitor Users in the product documentation.

The new Service Component Discovery feature is now a part of Dynamic Service Insights.

With this capability, LogicMonitor enables you to aggregate datapoints across subsets of service metrics. This means you can model your services with fewer service objects while still maintaining the granularity and visibility required for individual subservice components.

For more information, see Configuring Service Component Discovery in the product documentation.