v.229 Release Notes

LogicMonitor now supports monitoring for AWS Shield Advanced.

To access  this feature, navigate to Modules in LogicMonitor > Locate the AWS_Shield_Advanced module and select the AppliesTo tab.

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

Cost Optimizations Recommendations now detects idle Azure SQL databases, and recommends deleting unneeded database resources.

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

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

The Cost Optimization Billing landing page now provides cost analysis insights for cloud billing. The Cost Analysis tab displays current and historical cost breakdowns, costs by dimension, and cost anomalies.

These visualizations enable you focus on spending in specific areas, and make informed decisions to manage costs efficiently. You can quickly analyze spending across your cloud environments, and drill down into cost categories to track anomalies or increase in cloud spending.

To access this feature, navigate to Cost Optimization > Billing > select the Cost Analysis tab. For more information, see Cost Optimization – Billing in product documentation.

The Cost Optimization Billing landing page now provides more insights for cloud billing. Individual tabs within the Billing page now display general billing details, trends, and detailed cost analysis visualizations.

This enhanced configuration enables you to easily access specific cost details when observing your cloud spending. Each tab provides individual filtering options to further customize your billing observations.

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

You can now share Cost Optimization and Resource Explorer widgets when creating dashboard reports on LogicMonitor dashboards.

This enhancement enables you to create more comprehensive shared dashboard reports that include cloud resource usage and billing details.

For more information, see Dashboard Distribution in product documentation

You can now include the following widgets when sharing a dashboard report:

• Billing widget
• Billing Forecast widget
• Advanced Metrics widget

This enables you to email a dashboard snapshot that includes a visual report of your data or generate a dashboard report URL that you can share as needed.

To access this feature, navigate to Dashboards > select the dashboard you want to share that contains one of these widgets > select Manage Dashboard Options > Share Dashboard Report, and configure the share settings as needed.

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

The Map widget now complies with dashboard filters, enabling you to dynamically update a Map widget in addition to other filter-compliant widgets when you configure a dashboard filter.

To access this feature, navigate to a dashboard that contains a Map widget, or add a Map widget to a dashboard, and then configure the dashboard’s filter. The Map widget dynamically updates based on the configured filter.

For more information, see Modern Dashboards in the product documentation.

You can now set a default dashboard from the Appearance and Sounds settings in your Profile. This enables you to set a default dashboard for your profile if you do not have access to the Manage Dashboard settings of a dashboard.

If you previously set a dashboard as a default dashboard from the Manage Dashboard settings of the dashboard, entering a new dashboard as the default removes the previously set dashboard. This behavior is reflected in the Manage Dashboard settings for both the previously set default dashboard and the newly set default dashboard.

To access this feature, navigate to Profile > Appearance. You can set the default dashboard for your profile by entering a dashboard in the Dashboards setting.

For more information, see Appearance and Sounds in the product documentation.

Key feature names within LM Logs are now standardized to use LogicMonitor-specific identifiers, improving product clarity, recognition, and consistency across the platform.

These standardized names replace generic industry terms as follows:

• Log Analysis is now  renamed as LogAnalysis
• Log Pipelines is now  renamed as LogAlert Groups
• Log Alert Conditions is now renamed as LogAlerts
• Log Patterns is now renamed as LogPatterns

This new naming model improves search accuracy, content tagging, and user understanding across documentation, support resources, and UI elements.

For more information, see LogAnalysis, Accessing LogAnalysis, LogAnalysis Widgets, Filtering Logs using LogAnalysis, LogPatterns, LogAlert, and LogAlert Groups.

You can now organize, share, and manage Saved Queries in LM Logs more effectively using Shared and Public Query Groups. This enhancement simplifies collaboration and standardizes key log queries across teams and environments.

• Shared Query Groups enable selective sharing within specific users or teams for private or department-level analysis.

• Public Query Groups enable organization-wide visibility, supporting standardization and onboarding use cases.

To access this feature in the LM Logs Query Tracking Library, select the Views dropdown > Manage Saved Filters.

For more information, see Log Query Filters in the product documentation.

You can now visualize grouped log data in the Aggregate tab on the Logs page. This new view provides interactive charts to help you identify trends, proportional distributions, and metric summaries across log groups such as logLevel, application, and host.

The Aggregate tab supports multiple visualization types—Column, Line, Area, Pie, Donut, and Big Number, enabling you to view log patterns at a glance and filter logs directly from visual segments.

In addition, Big Number is now supported with the Logs DB widget. You can create and test your query and visualization in the Aggregate tab, then add it as a Logs DB widget to a new or existing dashboard for ongoing monitoring.

To access the feature, navigate to Logs > Aggregate, run a query, and select a chart type from the Chart type dropdown.

For more information, see Visualizing Log Data on the Aggregate Tab in the product documentation.

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 enhanced cisco.ucsx snippet now supports use of NetScan and Host properties.

The enhanced cisco.catalyst.center and cisco.sdwan snippets now add a standardized User-Agent header to all API requests for improved traceability and compliance.

You can now use the cisco.meraki snippet with collector versions that do not support cache removal. This enhancement improves compatibility and ensures consistent data collection across a wider range of collector versions.

The cisco.ucs snippet now supports configurable connection and read timeouts. You can specify custom values using the properties ucs.api.connectTimeout and ucs.api.readTimeout. This update enables you to better manage API connection reliability for your UCS integrations.

The vmware.vsphere.api snippet now features improved cache retrieval for vCenter tags. This enhancement enables faster and more efficient tag data retrieval, improving overall snippet performance.

The enhanced lm.emit snippet now automatically normalizes property keys before being emitted. This improvement ensures more consistent data handling and prevents key mismatches in emitted properties.

The lm.remote snippet now supports using Custom Challenge Response. This optional enhancement improves compatibility by adding support for a wider variety of authentication workflows when connecting to remote systems through Secure Shell Protocol (SSH).

The Cisco Meraki NetScan now checks for duplicate system.ips before adding resources to LogicMonitor. This enhancement enables you to maintain accurate device inventory by preventing duplicate devices from being added or updated incorrectly during the onboarding process.

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

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

In November, LogicMonitor EA Collector 39.100, will use Groovy 4 instead of Groovy 2.

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

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

The VMware_SDWAN modules have been removed and replaced by the new Arista VeloCloud SD-WAN monitoring package. These modules were incompatible with recent VeloCloud API rate limits, which caused data gaps and reduced monitoring reliability. The VMware_SDWAN modules are no longer accessible in the LogicMonitor Exchange. If these modules are in your My Module Toolbox, they now appear with a state change from “official” to “deprecated.”

The modules are not accessible in the LogicMonitor Exchange. If you have them in your My Module Toolbox, they will now display the with a change in state from “official” to “deprecated.”

The following modules have been removed from the Exchange:

• VMware_SDWAN_BGP_Sessions
• VMware_SDWAN_Health
• VMware_SDWAN_Interfaces
• VMware_SDWAN_Performance
• VMware_SDWAN_Topology
• VMware_SDWAN_Tunnels
• addCategory_VMwareSDWAN
• addERI_VMware_SDWAN
• VMware_SDWAN_Topology
• VMware SDWAN Alerts

You must migrate to the Arista VeloCloud SD-WAN monitoring package to maintain accurate and reliable monitoring of your SD-WAN devices. This replacement package provides enhanced performance and resolves the data gaps introduced by recent rate limits.

For more information, see Arista VeloCloud SD-WAN Monitoring in the product documentation.

A known issue affects DataSource bulk updates performed from your My Module Toolbox when the DataSource is applied to a large number of resources. To update impacted DataSources, select and update each one separately.

After you enable Instance Gold Config, the icon is disabled again once configuration data is collected. This allows you to re-enable Instance Gold Config, which is not the expected behavior.

Fixed an issue that caused instances moved from the Unmonitored Instances group to not update their group assignment, collection, or alerting status.

The property filter for resources on the Info tab in the Resource Tree does not function correctly when the filter text contains leading or trailing spaces or when it includes a glob expression beginning with an asterisk.

Remove any leading or trailing spaces from the filter text and avoid using glob expressions that start with an asterisk. The filter works as expected when text input is exact or when using standard wildcard placement within a string.

You can now use the new Debug permission to remotely execute diagnostic and troubleshooting commands directly on a Collector. This permission is required for running the Collector Debug Facility.

You must have administrator privileges to assign or manage the Debug permission.

For more information, see Settings Permissions from product documentation.

LogicMonitor now highlights Informational recommendations on the Security page, giving you improved visibility into advisory and optional configuration improvements. This helps you easily review best-practice updates and keep your portal aligned with the latest LogicMonitor standards.

For more information, see Security Settings in product documentation.

You can now restrict users to a single active session at a time to improve the account security and data integrity. Previously, users could maintain multiple simultaneous sessions across different browsers, devices, or IP addresses —a behavior that can cause unauthorized access and introduce data inconsistencies.
This enhancement strengthens account security, protects data integrity a provides improved visibility into active user sessions.

For more information, see Security Settings in product documentation.

You can now view usage metrics for Dynamic Service Insights (DSI) directly within Usage Reporting in the LogicMonitor portal. This enables faster analysis of DSI consumption patterns, by providing detailed insights through the usage contributors table and interactive graphs.

To access this feature, navigate to Settings > Usage, and select Dynamic Service Insights from the Product dropdown menu.

For more information, see Usage Reporting for DSI 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.

Usage reporting for devices may be delayed by up to two day at the beginning of the month. During this period, you may temporarily see zeros in your usage reports that do not reflect actual usage.