v.239 Release Notes

LogicMonitor now supports monitoring for AWS Managed Service for Prometheus.

To confirm this feature is available, navigate to Modules in LogicMonitor and locate AWS_ManagedPrometheus.

For more information, see Cloud Services and Resource Units in product documentation.

You can now use the dimension explorer to navigate available filter dimensions in Cost Optimization Billing. Use the dimension explorer to visualize billing dimensions that have existing filter properties, select filters based on your requirements, and find related properties to further refine your billing visualizations.

This enhancement simplifies finding effective filter properties, and enables you to build complex filters faster than searching and selecting individual properties from the list.

To access the dimension explorer, navigate to Cost Optimization > Billing. Select Add in the Filter By field, then select Help me choose.

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

You can now apply filters directly to Custom Graph widgets and control whether they interact with dashboard filters. You can manage widget-level filters independently. You can enable an override setting so the widget uses only its own filters, or disable it so both widget and dashboard filters are applied together. Settings carry over across UI and API operations, including export, import, clone, and duplicate.

When the toggle is on, the widget uses only widget-level filters. When the toggle is off, the widget applies both widget-level and dashboard-level filters together.

To access this feature, navigate to a dashboard and open a Custom Graph widget configuration.

For more information, see Custom Graph Widget Creation in the product documentation.

You can now configure the new Action Notes alert status on the integration pages for ticketing and communication services to update the comments or messages with a DiagnosticSource or RemediationSource output report in JSON or plain text format. Currently, you can configure the following:

• Workflow integrations—Custom HTTP delivery, Jira (JSM), ConnectWise, PagerDuty, ServiceNow, and AutoTask

• Communication integrations—Slack App and Microsoft Teams

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

• ##DIAGNOSTIC_SOURCE_OUTPUT##

• ##DIAGNOSTIC_SOURCE_STATUS##

• ##REMEDIATION_SOURCE_OUTPUT##

• ##REMEDIATION_SOURCE_STATUS##

• ##MESSAGE##

These tokens apply only to the Action Notes alert status for the supported integrations.
For more information, see LogicMonitor Integrations Overview in the product documentation

Webhook log sources now support attaching JSON data from webhook payloads as log field metadata. This enhancement enables you to enrich logs with contextual metadata, including strings, objects, arrays, and Boolean values, for improved filtering, parsing, and analysis.

To access this feature, while defining log fields, select Webhook Attribute from the Method dropdown menu to map values directly from the webhook payload.

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

You can now view log properties in a consistent, structured order to improve usability and help you locate related information efficiently.

Log properties are now sorted alphabetically, with _lm fields first, followed by other fields. Related fields are grouped together (for example, source_ip and source_dns), improving readability and enabling faster analysis. You can also select column headers to sort log properties by custom fields or _lm-generated fields.

You can now protect sensitive information in your log data with enhanced LogSource obfuscation capabilities for logs collected by a LM OTEL Collector.

This update ensures that sensitive fields (such as credentials, tokens, and personally identifiable information) are automatically masked during ingestion, reducing the risk of data exposure while maintaining log usability for troubleshooting and analysis.

You must upgrade to LM OTEL Collector version 6.1.00 or later.

To access this feature, configure a Log File LogSource and apply sensitive data masking using either the default masking rules or custom rules based on your requirements.

For more information, see Configuring Sensitive Data Masking for LogSource in the product documentation.

You can now perform SSH-based remediation actions on Linux hosts by using the Linux Remediation Monitoring package. This package enables remote process termination, process launch, and system reboot actions to help reduce service downtime and improve remediation workflows.

These modules use standard Linux utilities through SSH connectivity. Process matching requires an exact full command match, including arguments.

To access this feature, navigate to LogicMonitor Exchange and install the Linux RemediationSources Monitoring package.

For more information, see Linux RemediationSources Monitoring in the product documentation.

You can now automate remediation actions on Windows systems by using PowerShell remoting over WinRM. The Windows RemediationSources Monitoring package supports remote process control, system restart, cluster node maintenance, and disk cleanup operations to help improve service availability and reduce manual intervention.

Remediation actions run over WinRM by using the remediation-specific Windows credentials configured for the package, which can differ from the credentials used for standard Windows monitoring. These credentials have the privileges required for the selected remediation action. The package supports Windows Server 2012 R2 through Windows Server 2025

To access this feature, navigate to LogicMonitor Exchange and install the Windows RemediationSources Monitoring package.

For more information, see Windows RemediationSources Monitoring in the product documentation.

LogicMonitor now supports Automated Remediation to automatically run remediation scripts to fix problems in real time for affected resources. When an alert is triggered, instant diagnostic insights (using DiagnosticSource) and faster issue resolution (using RemediationSource) help reduce MTTR and keep systems running smoothly.
Automated Remediation enables you to do the following:

• Use out-of-the-box RemediationSource modules to remediate common issues such as high CPU utilization and increased memory usage.
• Manually configure a RemediationSource using Groovy or PowerShell scripts targeting specific issues.
• Automatically run RemediationSource scripts according to the sequence of stages configured in an Action Chain when conditions defined in an Action Rule are met.
• View usage data for Automated Diagnostics and Remediation (ADR).

To access Automated Remediation, you must meet the following requirements:

• Remediation Source permission for resources
• View or Manage permissions for Action Rules and Action Chains
• View permission for Usage settings
• The Enable Running Remediation Sources switch enabled on the Security page
• EA Collector 39.500 or later installed on your machine
• Active Automated Diagnostics and Remediation entitlement through an eligible LogicMonitor platform package or a standalone ADR subscription

To access RemediationSource, navigate to Settings > LogicModules. In the Add modal, select RemediationSource.

For more information, see Automated Diagnostics and Remediation Overview 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:

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

Enhanced Script NetScan now preserves existing resource properties that are not reported during discovery runs or dry-runs. You can now retain manually added properties while still updating reported property values and adding newly discovered properties. In addition, reported system.categories values continue to append to existing categories.

This enhancement also applies patch operations to resource groups and records update activity in audit logs and device discovery logs.

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

You can now filter Resource Inventory Reports using resource properties in the Filter By field. Matching properties are suggested as you enter values. You can add multiple filters, clear all filters, and include or exclude matching resources or instances.

For more information, see Resource Inventory Report in the product documentation.

As LogicMonitor continues to phase out the legacy UI, the New UI Preview switch will be removed from Resources, making Resources 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 in LM Community.

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

LogicMonitor has updated the LogicMonitor REST API v3 Swagger with the following new API endpoints:

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

LogicMonitor plans to transition synthetic monitoring capabilities from LM APM Synthetics (SYN) to Catchpoint 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, and Catchpoint represents the long-term direction for synthetic monitoring within the LogicMonitor platform. Catchpoint 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.

You can now view usage data for Automated Diagnostics and Remediation. The usage data provides visibility into on-demand and automated execution of diagnostic and remediation scripts across your LogicMonitor portal. The data enables you to monitor usage against the entitled execution quota.

On the Usage page, you can view the count of entitled daily quota, current daily executions, and historical daily executions. Usage is measured daily as the total executions run across your LogicMonitor portal. By default, the execution count for the current day of the month displays.

To access this feature, navigate to Settings > Usage, and select “Automated Diagnostics & Remediation” from the Product dropdown menu.

For more information, see Usage Reporting for Automated Diagnostics and Remediation in the product documentation.

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