v.222 Release Notes

The Cluster Alert Tuning tab for a resource now features a layout that improves visibility and accessibility. You can now review alert threshold criteria and take actions like edit, alert routing, and delete from a dedicated, inline Actions column. Each icon opens its respective form, allowing you to quickly update alert configurations.

The new LogicModule column links directly to the module that generated the alert, making it easier to trace and adjust alert definitions (access depends on your permissions).

You can now enable cluster alerts and optionally suppress individual alert notifications using two new switches in the tab. This gives you more granular control over alert behavior without needing to modify underlying modules.

You can also perform bulk actions such as enabling or disabling cluster alerts or notifications, or deleting entries by selecting rows and using the Actions dropdown menu.

For more information, see Cluster Alerts Management in the product documentation.

LogicMonitor now supports server monitoring for AWS Application Migration Service.

When you add a source server, LogicMonitor automatically detects a server and starts monitoring its health without additional configuration.

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

You can now include a Logs widget when sharing a dashboard report. This enables you to email a dashboard snapshot that includes a visual report of your LM Logs 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 a Logs widget > select Manage Dashboard Options > Share Dashboard Report, and configure the share settings as needed.

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

You can now include a hyperlink when configuring the Big Number widget. This enables you to provide access to pages in your portal or other destination as needed. For example, you could include a link to the Alerts page so that when selected, you can access the Alerts page directly from the widget.

To access this feature, navigate to Dashboards > Add Widget > Big Number. Add the hyperlink when configuring the Number settings.

For more information, see Big Number Widget in the product documentation.

You can now create and manage ConnectWise configurations from LogicMonitor Resources using the new Configuration Sync feature. This feature enables automated mapping between LogicMonitor resource properties and ConnectWise configurations, ensuring data consistency between platforms. Delta syncs run every 30 minutes, while full syncs can be initiated every 7 days.

Configuration Sync includes the following capabilities:

• Map LogicMonitor resource properties to ConnectWise questions and configuration details.
• Map LogicMonitor resource types to ConnectWise configuration types.
• Link LogicMonitor tenants to ConnectWise companies for accurate account assignments.

For more information, see ConnectWise Integration in the Product Documentation.

LogicMonitor has increased the total number of log pipelines per portal to 20, giving you greater flexibility in organizing your alert logic across different resource types or teams. Each log pipeline now supports up to 55 alert conditions, an increase from the previous limit of 20.

Within the 55 alert conditions, you can do the following:

• You can now create up to 10 time-window based alert conditions per pipeline. These alerts trigger when one or more logs match the defined criteria within a specified time window such as 10 minutes, 30 minutes, 1 hour, 8 hours, or 1 day.
• You can also configure up to 10 stateful alert conditions per pipeline to track repeating log patterns or sequences.

For more information, see the Log Alert Conditions 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 lm.remote snippet now supports SSH key passphrases. You can enable this functionality by setting either of the following properties:

• ssh.cert.pass
• ssh.publickey.pass

The updated Enhanced Script NetScan includes improved logic for determining Cisco Catalyst Center versions, ensuring the correct API endpoint is used for versions 2.3.7.6 and later.

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

The cisco.meraki.cloud snippet now handles API errors more effectively when collecting data from the VPN statistics and status endpoints. It specifically accounts for the following responses:

• • "Please reduce 'perPage'"
  • "Please reduce 'timespan'"

These enhancements improve the reliability of data collection from the Meraki API.

The updated lm.data.topo snippet introduces improved discovery for Checkpoint Firewalls. You can now identify more granular topology data for Check Point infrastructure.

LogicMonitor now has support for configurable retention periods for deleted data source instances, allowing users to control how long deleted instances remain in the database and cache before permanent removal.

Users can choose to retain deleted instances for 0, 1, or 2 days, providing flexibility for auditing or rollback needs. This functionality is currently enabled for the following DataSources: BGP-, Cisco_EIGRP_Peers, Cisco_ISIS_Neighbors, ISIS_Neighbors, and OSPF_Neighbors. For more information, see Automatically Delete Instance in product documentation.

The enhanced lm.topo snippet now supports edge status. This enhancement improves visibility into relationships between monitored resources.

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 will be 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 Collector 37.100, which is 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 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 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() 

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:

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 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]

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 

The LogSource module no longer displays inline support articles automatically within the support panel. Users can still access the support panel manually, but it no longer opens directly to the relevant article for this module type. This is a temporary behavior change introduced to prevent functional issues related to pre-caching support articles. A long-term refactor is planned.

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

You can now create an Alert report that includes historical SDT information for your resources. This provides you visibility into whether an alert was generated for a specific resource that was put into SDT for the configured timeframe of the report.

This information is displayed as a column when configuring the report and in the table of the generated report. If there is an active SDT during the lifecycle of an alert, the value in the column is marked as “True.” In addition, you can filter the alerts to include or exclude the historical SDT information.

To access this feature, navigate to Reports and add an Alert report. The historical SDT information displays in the Report Preview when configuring the report.

For more information, see Alerts Report in the product documentation.

Creating an adhoc Alert report in CSV format with the maximum request threshold fails with the following error in logs:

java.lang.OutOfMemoryError

As a result of the migration of SAML1 to SAML2, users authenticated using SAML-based Single Sign-On (SSO) may be logged out. Only SAML-based SSO users are affected. Standard user sessions remain unaffected.

Users can log in again after the upgrade completes.

LogicMonitor OpenTelemetry Collector (lmotel) has been updated to version 5.2.00 and includes the following updates:

• LogicMonitor now has improved log-to-resource mapping, which maps logs to the correct cloud resource instead of defaulting to the collector host.
  Previously, logs were mapped to the lmotel resource. Unmapped logs will be treated as resourceless.
• Added POSIX-compliant installer to enable broader compatibility and smoother installation across various Unix-like systems.

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

You can now enable Two-Factor Authentication and Restrict Single-Sign-On simultaneously. Previously, if you selected Restrict Single Sign On, it disabled the ability to enforce Two-Factor Authentication.

For more information, see Enabling Single Sign-on in the product documentation.

LogicMonitor has now added a new Modules: Manage permission to Access Groups in the My Module Toolbox. This permission lets you fully manage modules mapped to their Access Group, including creating, cloning, installing, importing, deleting, and editing AppliesTo fields. Unlike the existing Manage (Limited) permission, the new permission provides full control, including the ability to create and delete modules.

In addition, Access Groups now supports tenancy. If an access group with tenancy is selected, the module auto-populates appliesTo with the tenant information (system.tenant.identifier property).

For more information, see Access Group Permissions and Tenant Identifier Property Name in the product documentation.