v.230 Release Notes

You can now monitor the status of VWAN VPN connection links with the new Microsoft_Azure_VwanVpnLinkConnection DataSource.

This enables you to detect VPN connections on VPN Gateway within an Azure Virtual WAN and view the status of VPN links.

You can now filter the Microsoft_Azure_BackupJobStatus datasource using Active Discovery.

This enables you to filter individual DataSource instances by properties such as “backupmanagementtype” or “operation.”

For more information, see Active Discovery in the product documentation.

Cost Optimization Billing now supports configuration and billing data for GCP billing. This enables you to view GCP billing data in your Billing dashboards, alongside AWS and Azure.

You must configure Billing to gather billing data from a GCP billing export. For more information, see Cost Optimization Billing Configuration in product documentation.

You can now perform various actions on a Pie Chart 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 specific slice of the pie chart and navigate directly to Resources in the Resource Tree to view the data for that instance.

To access this feature, navigate to Dashboards, and add a Pie Chart widget to the Dashboard. Select a slice in the chart to display the options for the actions.

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

You can now view and manage all tracked log queries in one centralized location using the Query Tracking Management page. This enables administrators and users with appropriate permissions to pause, resume, delete, and filter tracked queries directly from the LogicMonitor portal.

To access the Tracked Query Management page, navigate to Logs > More Options > Logs Management and select the Tracked Queries tab.

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

The LM Logs Enterprise Usage page now includes enhanced usage reporting for Log Partitions, providing improved visibility into log data consumption across your portal. This update enables you to monitor ingestion trends, analyze partition-level usage, and compare data stored under different retention policies.

The updates include the following key enhancements:

• Introduced Partitions (Tenant.Identifier) to filter usage data by partition or tenant.
• Added Subscription Type filters for Yearly Retention and 7-Day Retention plans to compare data stored under different retention periods.
• Added a View Partitions option that opens the Log Partitions page from the Usage view for quick access to partition management.

To access this feature, navigate to Settings > Usage > LM Logs Enterprise, and select Partitions (Tenant.Identifier) from  Contributor type.

For more information, see Usage Data for LM Logs Enterprise in the product documentation.

The Log Partitions feature in LM Logs Enterprise has been enhanced to provide greater visibility and control over log data management. This enhancement enables administrators to define and manage partitioned log data for improved performance, governance, and scalability.

This enhancement enables you to do the following:

• Mix and match retention SKUs within a single portal—supporting multiple retention tiers (for example,7-day, 30-day, 90-day, and 1-year) across different log types.
• For example, you can retain Network Logs for 30 days and Windows Logs for one year within the same portal.
• Optimize query performance through partitioned data structures that enable faster search execution.
• Simplify data lifecycle management by applying unique retention policies and naming conventions per partition.
• Define organizational structures that support cost management, compliance, and operational segmentation.
• Set enforceable limits on partitions to prevent data overages, ensuring predictable storage utilization and mitigating ingestion risk for expanded log types and new resources.

Your LogicMonitor portal must have the Logs feature enabled.
Feature availability may depend on your subscription level and RBAC permissions.

To access Log Partitions, navigate to Logs > More Options > Log Partitions.

For more information, see Log Partitions in the product documentation.

When viewing the Logs tab under Settings > Account Information > Portal Information, the counts for Partitions, LogAlert Groups, LogAlerts, and Tracked Queries display as 0, even when these objects exist in the portal.

This issue occurs only when no tracked queries are present on the portal on the first day of portal setup. The data displays correctly when tracked queries are created.

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 lm.data.topo snippet now identifies Arista Networks EOS routing-enabled switches as switches rather than routers using the Switch ERT. This change enables more accurate device classification within topology mapping, improving visibility and management efficiency.

The enhanced VeloCloud SD-WAN NetScan now adds the enterprise ID property to onboarded resources and includes the enterprise ID in API requests.

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

LogicMonitor now supports Automated Diagnostics to resolve issues faster with instant diagnostic insights. To diagnose issues, Automated Diagnostics captures real-time data when an alert is triggered that helps to analyze root cause of the issue, cut MTTR, and run systems smoothly.

Automated Diagnostics enables you to do the following:

• Diagnose issues and analyze root cause of issues in your LogicMonitor portal.
• Manually configure a DiagnosticSource using Groovy or PowerShell diagnostics script targeting a specific issue such as high CPU utilization or increased memory usage.
• Support for out-of-the-box DiagnosticSource modules to diagnose issues.
• Manually run DiagnosticSource for resources.
• Create Diagnostic Rule to define conditions where an alert can automatically run a DiagnosticSource module.

For more information, see Automated Diagnostics Overview 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 December, 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]

Fixed an issue affecting NetScan properties in the Cisco UCS-X NetScan script. This fix adds support for host properties and NetScan properties, improving the accuracy and completeness of property data collected during Cisco UCS-X NetScan operations.

For more information see the Cisco UCS-X monitoring product documentation.

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: 

On the Resources page, when you select Graph Definition from a graph, the Graphs tab under Edit Datasource > Graphs should remain selected. However, after opening the module page, the tab briefly stays on Graphs before automatically switching to the Local History tab.

To mitigate this issue, you can manually reselect the Graphs tab to continue editing.

CAPTCHA verification is now triggered after a total of five invalid authentication attempts across all Two-Factor Authentication (2FA) modes combined. For example, this includes two invalid SMS attempts and three invalid email attempts, or five invalid email attempts altogether.

For more information, see LogicMonitor Two-Factor Authentication Overview from 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.