v.228 Release Notes

LogicMonitor has enhanced the Alerts page with a redesigned filter to provide a consistent and streamlined workflow. The existing funnel menu is now replaced with a standard filter design used consistently throughout the platform. For easy access, the Quick Filter option is now available as a button.

In LogicMonitor, navigate to the Alerts page and then from the Filter by: field, select a filter category and select a filter. Use Quick Filter for one-step filtering.

For more information, see Managing Alerts from the Alerts Page.

Azure Virtual Machine (VM) monitoring now captures additional properties when adding spot instance VMs to LogicMonitor. The additional properties priority and evictionPolicy now automatically apply to any spot instance VMs in the Resource Tree.

This enhancement enables you to account specifically for spot instance Azure VMs in your environment monitoring, and enables you to sort and filter your Azure resources by spot instance properties.

To view additional properties on your spot instance VMs, navigate to Resource Tree and select your Azure VM and select the Info tab to view both new properties.

LogicMonitor now supports monitoring OCI Compute, Block Storage, Object Storage, and Autonomous Databases through native API integration. This expanded support enables customers running OCI environments to include those resources in their cloud monitoring operations through LogicMonitor.

To monitor OCI resources, in LogicMonitor navigate to the Resource Tree and select Add > Cloud and SaaS > Oracle Cloud Infrastructure.

For more information, see OCI Monitoring Setup in product documentation.

You can now perform various actions on a Custom Graph 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 line on the graph and navigate directly to Resources to view the data for that instance in the Resource Tree.

To access this feature, navigate to Dashboards, and add a Custom Graph widget to the Dashboard. Select a line on the graph to display the options for the actions.

LogicMonitor now provides the Advanced Metrics widget that enables you to display an aggregation of metrics across multiple DataSources and visually represent the data similar to a Custom Graph widget, Big Number widget, Pie Chart widget, or a Gauge widget. The enhanced flexibility provided by the Advanced Metrics widget’s visualization options enables you to more effectively highlight the data most relevant to identifying root causes, prioritizing alerts, and reducing time to resolution.

The Advanced Metrics widget provides you the following visualization options to display your data:

• Line Graph
• Area Graph
• Stack Graph
• Big Number
• Pie Chart
• Donut Chart
• Gauge

The Advanced Metrics widget leverages the LogicMonitor Query Language (LMQL) to extend LogicMonitor’s platform giving you greater control and flexibility in how you query, filter, and visualize your data. LMQL uses a query-based approach to analyze large data sets, customize visualizations, and extract meaningful insights.

To access this feature, navigate to Dashboards > select Add for the Advanced Metrics widget.

For more information, see Advanced Metrics Widget and LogicMonitor Query Language (LMQL) Reference for Advanced Metrics Widget in the product documentation.

LogicMonitor now uses the enhanced JQL search API (/rest/api/3/search/jql) to improve search capability and future compatibility with Atlassian Cloud REST API v3. Ensure that your Atlassian account is configured to support Atlassian Cloud REST API v3.

The following API changes are supported:

Deprecated API: Search for issues using JQL (GET) Deprecated

New API : Search for issues using JQL enhanced search (GET)

You can now send webhook events directly from external systems to LogicMonitor. This facilitates real-time alerting without using a collector and without exceeding vendors’ API rate limits.

The following are the benefits of using Webhooks for sending event-driven data are:

• Streamlined data flow – Receive events instantly from systems that support webhooks with Bearer Token Authorization.

• Improved monitoring – Correlate external alerts with existing LogicMonitor metrics and logs for deeper insights.

• Broad source support – Collect data from cloud services, SaaS, cloud managed networking platforms (for example, Cisco Meraki, Juniper Mist, Ruckus One, and so on), and data protection platforms (for example, Rubrik Security Cloud).

For more information, see Webhook LogSource Configuration 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 Cisco Catalyst Center NetScan now supports the cisco.catalyst.center.device.ip property, which identifies the IP address assigned to a device at the time of onboarding. In addition, the Cisco Catalyst Center NetScan also supports filtering results by device family using the cisco.catalyst.center.device.family attribute. These enhancements enable you to search and manage devices more efficiently.

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

The Juniper Mist NetScan now supports handling of null secondary node names. This enhancement ensures that device discovery and reporting remain accurate even when secondary node names are not available.

For more information see Juniper Mist Monitoring in the product documentation.

The vmware.vsphere.api snippet now supports improved handling of API versions by recognizing differences in response data structures between vSphere API 7.0.1 or earlier versions. The snippet also provides enhanced error messages when monitoring API connection failures. These enhancements improve reliability and troubleshooting.

For more information, see VMware vSphere 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: 

LogicMonitor has now added importjson endpoints to REST API v3 Swagger, Python SDK, and Go SDK files. The following table display the new endpoints:

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.

You can now view usage reporting for Hybrid Resource Units. Hybrid Units provide a single, flexible measure of consumption that works across resource types. This enables you to monitor hybrid environments more efficiently while reducing subscription complexity and minimizing overage risk. LogicMonitor calculates usage as the monthly average count of hybrid resources.

You must be on a Platform Package that includes Hybrid Resources to view usage data.

To access this feature, in LogicMonitor, navigate to Settings > Usage > and select “Hybrid Resources” from the Product dropdown menu.

For more information, see Usage Reporting for Hybrid Resource Units in the product documentation.