v.233 Release Notes

LogicMonitor alerts now display the level from which an effective alert configuration was picked, in addition to the effective threshold that generated the alert.

You can leverage the following new tokens in alert messaging to track threshold inheritance:

• Effective threshold level—The threshold level from which the alert was originally generated.
• Alert trigger interval—The interval at which an alert is triggered.
• Alert clear interval—The interval at which an alert is cleared.

This enables you to easily identify the effective alert threshold level if the threshold was modified, or an auto-grouped device was moved to another device group.

For more information, see Tokens Available in LogicMonitor Alert Messaging in product documentation.

You can now view cloud resource costs within Resource Explorer detail panels using the Cost tab. This enhancement enables you to view cost data from the Cost Optimization feature for a particular resource, and quickly access Cost Analysis for more details.

To access this feature, navigate to Resource Explorer > select a resource > Cost tab.

For more information on navigating Resource Explorer, see Resource Explorer Overview in product documentation.

Cost Optimization Billing now supports FOCUS 1.2 for AWS Cost and Usage data exports. This enhancement adds fields generated by data exports in the FOCUS 1.2 schema to the Cost Optimization Billing display and filter properties.

For more information on configuring AWS billing data, see Cost Optimization Billing Configuration in product documentation.

As LogicMonitor continues to phase out the legacy UI, the New UI Preview switch will be removed from Dashboards, making Dashboards 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, including timeline and further updates about the removal, see Upcoming End-of-Life (EOL) for UIv3 Dashboards in LM Community.

For the most up-to-date information about Dashboards, see Dashboards Overview in the product documentation.

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

You can now compare log patterns across two time periods directly from the Alerts page using the new Compare Patterns functionality. This enhancement helps you quickly identify changes in log behavior, such as increases, drops, new patterns, or missing patterns without leaving the alert investigation workflow.

To access this feature on the Alerts tab, toggle the Show LogPatterns switch and select Compare.

For more information, see Viewing LogPatterns from Alerts page in the product documentation.

You can now organize tracked queries more effectively by creating custom groups in the tracked query library. Tracked query groups help you categorize and manage related tracked queries within Log Query Library, making it easier to maintain large or complex query libraries.

To access this feature, navigate to Logs > Manage Saved Filters > Tracked queries, then select Add new Group.

For more information, see Logs Query Tracking 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

You can now monitor the health and performance of HPE Aruba Networking CX Series switches with real-time visibility into CPU, memory, temperature, fan, power supply, and VSF stack metrics.

This new LogicModules monitoring package uses SNMP-based data collection and Aruba-specific MIBs to track hardware status and performance on Aruba CX switches. Compatible resources are automatically detected and assigned the required category for monitoring.

To access this feature, navigate to Modules > Exchange and install the HPE Aruba CX Switch Monitoring LogicModules.

For more information, see HPE Aruba CX Switch 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, 37.300, and 39.100 are now available and 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] 

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 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, 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 include custom host properties in SLA reports so you can deliver client-ready reports that combine SLA metrics with relevant resource metadata. This enhancement enables you to generate detailed reports directly from LogicMonitor, reducing the need for manual post-processing, lowering operational overhead, and improving scalability when supporting large customer bases.

The custom host properties display as custom columns alongside SLA metrics such as uptime percentage, threshold, an unavailability duration in exported reports. You can save custom column selections as reusable report templates to support different reporting needs.

To access this feature, navigate to Reports, and add an SLA Report.

For more information, see Service Level Agreement Report in the product documentation.

Administrators can now enable or disable individual two-factor authentication (2FA) methods for user login and setup, including passkey, authenticator app, SMS, voice call, and email. This gives you greater control over available authentication methods, helping align portal access with your organization’s security and compliance requirements.

Only 2FA methods that have been configured display as options. For example, the passkey option is shown only if passkeys have been set up.

To access this feature, navigate to Settings > Security.
For more information, see Two-Factor Authentication in the product documentation.

Service management now enforces rule-controlled behavior for services created using DSI. When managing a service, you can now edit description, assign a Collector, add custom properties and groups to the rule-based service.

For services created using DSI, the Name field is read-only. Changes to rule-defined properties or groups are overridden during the next rule evaluation, while members and metrics must be updated using the service rule or the associated LogicModule.

To access this enhancement, navigate to Services and select Manage.
For more information, see Adding a Service in the product documentation.

You can now edit Service Auto-Creation rules that have never been activated. For inactive rules that are not yet run, all fields are editable.

When a rule is run at least once, editing is intentionally restricted to protect existing services. In this case, you can update only the rule name, description, service criticality, membership re-evaluation interval, and new properties added to each service.

You cannot modify core rule logic such as Group By and Filter By fields, after activating the rule, even if the rule is later deactivated.

In addition, Service Auto-Creation rules now support multiple service group hierarchies, enabling you to preview and configure up to three service group hierarchies per rule.

To access this, navigate to Services > Service Auto-Creation Rules > Actions > Manage.

For more information, see Adding Services Using Auto Creation Rules in the product documentation.

You can now configure Topology Map Edge Status to include custom metric, threshold settings, and edge colour. These custom settings apply consistently on the specific topology saved map, topology widget on dashboard that improves edge connection health visibility and issue detection.

To access this configuration, navigate to Mappings > Saved Maps.
Toggle the Edge Status switch and then select Customize Metrics.

For more information, see Using Edge Status in the product documentation.

In a future release of LogicMonitor, support for legacy LM Container builds and Argus versions 5, 6, 7, and 8 will be discontinued. 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
• The latest security patches and compliance updates required for modern Kubernetes environments
• Ongoing compatibility with newer Kubernetes versions and container runtimes

You can migrate existing Kubernetes cluster configurations using either of the following methods in the product documentation:

• Migrating Existing Configurations Using Helm
• Migrating Existing Configuration Without Using Helm

For more information about this deprecation, including timeline and further updates about the removal, see Upcoming End of Life (EOL) for Legacy Versions 5, 6, 7, and 8 for Legacy LM Container & Argus in the LM Community.

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