The Cost Optimization Recommendations now notify users if datasources or datapoints are not configured properly to generate recommendations. A warning notice is displayed on the dashboard, which you can expand to view the status and recommended actions.

For more information, see Cloud Optimization – Recommendations.

Support for Azure datasources in Cost Optimization Recommendations is now generally available to subscribed customers. Recommendations are now provided for the following Azure datasources:

• Idle Virtual Machines
• Underutilized Virtual Machines
• Unattached Azure Disks

For more information, see Cloud Optimization – Recommendations.

The Cost Optimization Recommendations now notify users if datasources or datapoints are not configured properly to generate recommendations. A warning notice is displayed on the dashboard, which you can expand to view the status and recommended actions.

For more information, see Cloud Optimization – Recommendations.

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

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 v.214 Modules 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.

When running a module using Apache Groovy 4, and using java.util.Date.format(), the following exception is thrown:

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

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

Important: LogicMonitor is releasing updates to LogicModules to mitigate this issue for official LogicMonitor-provided modules.

When running a module using Apache Groovy 4, and using the groovy.json.JsonSlurper(), the following exception is thrown:

exception:groovy.lang.RunTimeException: Unable to load FastStringService

Note: This issue is fixed with the LogicMonitor Collector version 36.200 or later. To mitigate this issue when running a module using Apache Groovy 4, ensure you upgrade to the LogicMonitor Collector version 36.200 or later.

LogicMonitor has now updated LogicMonitor REST API v3 Swagger, v3 Python, and v3 GO SDK files with new endpoints under the Partitions category. These endpoints will be available for use only when the Partitions feature is enabled for you. To access this feature, contact your LogicMonitor Customer Success Manager.

The Swagger and SDK files will be available after the v214 deployment to production is complete.

For more information, see REST API Change Log and REST API v3 Swagger Documentation.