v.224 Release Notes

Recommendations now identifies Azure Virtual Machines in a “stopped” state and suggests de-allocating or terminating them. This recommendation type helps prevent unnecessary costs generated by Azure for allocated resources on inactive VMs.

Additionally, Idle AWS EC2 Instance and Azure VM recommendations now suggest changing to a smaller size, in addition to terminating the resource. This provides more flexibility for users who want to reduce costs without removing resources they may need later.

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

Billing widgets in LogicMonitor Dashboards now support the Big Number with Trend visualization, enabling you to highlight key performance indicators (KPIs), such as total cost, with a single numeric value and accompanying trend line.

This provides immediate visibility into billing performance without the distraction of additional visuals.

The Grouped Table visualization is now enhanced to include an inline breakout graph of trending costs. This enables you to easily visualize trends in billing data without creating additional widgets. To access the graph, select View Graph Info within an existing Grouped Table widget.

For more information, see Billing Widget in product documentation.

You can now save a filter as a default filter view to enable you to duplicate dashboard-level filtering. This enhancement eliminates the need to manually re-create the filter for each new dashboard, and ensures a streamlined and consistent dashboard setup process. In addition, when you clone a dashboard, you can clone the dashboard’s associated filters to create a default filter for other users in your organization.

When you create the default filter, you add properties to create the filter, and then set the filter you created as the default filter. You can create the default filter using the filter settings in the dashboard. Alternatively, you can use the Default filter settings in the Manage Dashboard settings. A previously created default filter persists between the filter settings in the dashboard and the Manage Dashboard settings.

Users that leverage the default filter can rename the filter as needed while retaining the properties the filter was configured with.

For more information, see the following in the product documentation:

Dashboard Filters
Dashboard Management
Dashboard Creation

The updated cisco.catalyst.center snippet now significantly reduces the volume of cached data on collectors. Cached data is scoped exclusively to devices actively monitored by the respective collector, improving overall memory efficiency and performance.

For more information, see Cisco Catalyst Center 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 Catalyst Center NetScan now supports filtering by serial number, IP address, and site. This enhancement enables faster identification and validation of specific resources during network discovery.

For more information, see Cisco Catalyst Center 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, will 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]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

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

The Enhanced Script NetScan now includes a deduplication framework for Cisco Meraki Wireless Access Points and Cameras. When a newly discovered Meraki device includes a meraki.serial value that matches the auto.endpoint.serial_number of an existing resource, LogicMonitor updates the existing resource with the new hostname and IP address instead of creating a duplicate. This improves device tracking accuracy and reduces the need for manual cleanup in DHCP-based networks.

For more information, see Enhanced Script NetScan Overview.

You can now choose the following commonly monitored time range options when creating a report:

• Week to date
• Month to date
• Quarter to date
• Year to date

This enhancement streamlines report creation by reducing manual configuration, minimizes errors from manual date selection, and ensures consistency across teams using standardized timeframes.

These new options are available for all report types that support a date range.

For more information about configuring a specific report, see Choosing a Report Type in the product documentation.

Fixed an issue that caused an adhoc Alert reported created in CSV format with the maximum request threshold to fail with the following error in logs:

java.lang.OutOfMemoryError

This release adds new Cost Optimization Recommendations endpoints to the LogicMonitor REST API v3. Updates have been made to the API v3 Swagger, Python SDK, and Go SDK files.

For more information, see the and the . These updates will be available after LogicMonitor v224 is deployed to production.

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

To strengthen security, LogicMonitor REST API v3 Swagger now includes the x-minimum-permissions metadata in the Extensions section of each API request. This metadata specifies the minimum permission required to access the API endpoint. The update will be available after LogicMonitor v224 is deployed to production.

You can now create and configure OpenAI resources direction from the Resource Tree using the OpenAI resource wizard. Use this wizard to quickly configure a new OpenAI resource, organize it within resource groups, and configure properties to customize your OpenAI monitoring.

To create a new OpenAI resource, navigate to the Resource Tree page and select Add. Select AI and LLMs, then select Add for OpenAI. For more information, see OpenAI Monitoring in product documentation.

You can now enable or disable email notifications for important user account changes such as username updates, phone number changes, password resets, and so on. This enhancement gives you greater visibility and control over account activities, ensuring the security of your account.

To access this feature, navigate to Settings > Security. The Enable Email Notification switch is enabled by default for all users.

For more information, see Security Settings from the product documentation.

You can now preset the number of days after which the Enable Collector Debug switch is automatically disabled. By default, the switch remains disabled. When you enable the switch, a dropdown menu displays, enabling you to select the disable-after duration.

If the Enable Collector Debug switch is already enabled in V223 or earlier, then the disable-after duration is automatically set to ‘Never’.

For more information, see Security Settings 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.

Out-of-the-box users with the default administrator role can now self-activate their accounts when suspended due to inactivity.

Previously, if all users—including admins—were suspended due to inactivity, you required backend support for recovery. Admins can now recover suspended accounts due to inactivity without backend support. If you are locked out, you will receive an email with a recovery link to reset their password and regain access, ensuring continued portal availability.

For more information, see Security Settings.