v.240 Release Notes

On the Collector Logs page, you can now bulk update log levels for all or multiple Collector components simultaneously. To do so, select the checkbox for the required components, or to update the log level of all the components, select the checkbox in the table header and then select a log level from the Log Level dropdown menu. The log level is applied to all the selected components at once.

To access this feature, navigate to Settings > Collectors. Select a Collector and in the Logs tab select Manage Collector Logs.

For more information, see Managing Collector Logs in the product documentation.

You can now configure widget-level filters for Pie chart widgets independently from dashboard-level filters.

When widget-level filters are configured, you can enable the following override option: “Allow the widget level filters to override the dashboard filters.” When enabled, only widget-level filters apply. When disabled, both dashboard-level and widget-level filters apply together.

Widget-level filters and override settings are preserved across widget CRUD operations, APIs, export, import, clone, duplicate, shared widgets, and dashboard reports. Shared widget views and reports display data consistent with the dashboard view.

To access this feature, navigate to Pie chart widget configuration settings within a dashboard.

For more information, see Pie Chart Widget in the product documentation.

You can now display resource and instance properties as columns in table visualizations within the Advanced Metric Widget, which provides additional context alongside metric data and improves data interpretation.

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

You can now configure custom emails to share a DiagnosticSource and RemediationSource output in plain text in email content. This enhancement enables you to view diagnostic and remediation details directly within email notifications when output is available for an alert.

When a DiagnosticSource or RemediationSource output is available for an alert, you can use the following tokens to configure email content:

• ##DIAGNOSTIC_SOURCE_OUTPUT##

• ##DIAGNOSTIC_SOURCE_STATUS##

• ##REMEDIATION_SOURCE_OUTPUT##

• ##REMEDIATION_SOURCE_STATUS##

• ##MESSAGE##

For more information, see Custom Email Delivery in the product documentation.

You can now monitor the health and performance of Veeam Backup and Replication (VBR) infrastructure by using the Veeam Backup and Replication v13 REST API Monitoring package. This package provides visibility into backup jobs, session health, repositories, proxies, license usage, configuration backup protection, and Security and Compliance Analyzer findings.

This package uses the VBR REST API and supports VBR 13 with REST API revision 1.3-rev1. For more information see, Veeam Backup & Replication REST API (1.3-rev1) from Veeam.

To access this feature, navigate to LogicMonitor Exchange and install the Veeam Backup & Replication v13 REST API Monitoring package.

For more information, see Veeam Backup and Replication for REST API Monitoring in the product documentation.

The enhanced Nutanix Prism Central NetScan reads the optional netscan property nutanix.prism.ignore.proxy. When enabled, discovered Nutanix hypervisor resources are created with matching host properties so ongoing monitoring uses the same direct-connection behavior as the netscan run.

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

You can now use the optional NetScan property cisco.catalyst.center.status to filter Cisco Catalyst Center resources during discovery. This enhancement enables you to include or exclude resources based on the following status values: Unassociated, SUCCESS, or Managed.

This filter is particularly useful when you want to exclude unassociated resources that are no longer in use but continue to appear in Cisco Catalyst Center for several weeks after decommissioning.

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

The enhanced lm.data.topo snippet expands external resource type (ERT) identification and classification used by the addERI_Device and addERI_Cisco PropertySources. You can now achieve more accurate topology mapping and DAM dependency analysis through improved ERT assignment and reduced Unknown classifications.

The update adds classification support for the following:

• Cameras—including additional camera vendors

• Switches—including Omnitron iConverter GM4-HPOE resources and Cisco switches running Cisco IOS Software, CMICR Software keyword rule. The addERI_Cisco PropertySource now classifies CMICR-class Cisco switches as Switch instead of Unknown.

• Storage—including Lenovo DS4200 resources

• UPS and PDU resources—including Server Technology and APC SysOID mappings. New keyword rules identify Sentry Smart PDU, Watchdog 15, and generic PDU resources. Eaton ePDU resources are now classified as PDU instead of Unknown. Resources reporting NetVision7 in auto.endpoint.model or system.sysinfo are now classified as UPS instead of Unknown.

• Virtual machines—including ClearPass Policy Manager

• Wireless access points—including Aruba, Cambium, and Cloud Managed AP resources

• Cisco access points—including Cisco C8500 switches, and Cisco IOS c8000aep routers

You update and use the enhanced lm.data.topo snippet with the addERI_Device and addERI_Cisco PropertySources.

You can now specify alert properties in Groovy and PowerShell scripts when configuring a DiagnosticSource and RemediationSource. Alert properties enable scripts to use alert-specific context such as the affected instance, datapoint, or threshold value as input for conditional logic, enabling more targeted and relevant diagnostic or remediation actions. You can use inline token (##TOKEN## format) substitution in the Groovy and PowerShell scripts. You can also use runtime variable access in the Groovy script.

To use alert properties, you must install EA Collector 40.200 or later on your machine.

For more information, see Alert Properties for DiagnosticSource and RemediationSource Scripts 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, 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:

You can now centrally manage sensitive data masking policies for OpenTelemetry (OTEL) logs using a configurable Masking Rules table. The masking framework supports both regex-based rules to identify and mask sensitive information that matches specified patterns and JSON key-based rules to mask values for configured keys in structured log payloads.

You can now define and manage masking rules based on your security and compliance requirements to protect sensitive information across OTEL log data.

To use this feature, upgrade to LogicMonitor OpenTelemetry Collector 6.1.00 or later.

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

You can now filter resources and DataSource instances in supported reports using custom, system, inherited, and instance properties directly within report configurations.

You can apply include or exclude logic with exact match (EQ) or pattern matching (REGEX) operators to return only matching resources and metrics. This enhancement supports filtering behavior consistent with Santaba Dashboard Filter Property functionality.

To access this feature, navigate to the report configuration settings for supported Inventory Reports or Metric Reports.

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

You can now select multiple weekdays for a monthly (day-of-week) SDT. This enables a single SDT to apply to multiple days within the same week. You configure an SDT using the monthly (day-of-week) option and select the applicable weekdays.

For more information, see Resource SDT from the product documentation.

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.

For more information about this deprecation, see Upcoming End-of-Life (EOL) for UIv3 Resources (Including UIv3 Services) in LM Community.

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

A new Config tab is now available on the Service Details page, providing direct access to service configuration details.

The Config tab displays configuration data collected from ConfigSources and enables you to compare it with previous versions to review configuration changes without leaving the service context.

To access this feature, navigate to Services > select a service > Config.

For more information, see Config Tab in the product documentation.

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.

For more information about this transition, including roadmap details and evaluation guidance, see the Upcoming End of Life for LM APM Synthetics in LM Community.

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