v.212 Release Notes

LogicMonitor now offers an Enhanced Detection feature for AWS EC2 instances and Azure Virtual Machines. This new feature decreases latency of detecting new devices, and status changes of existing devices.

You must enable Enhanced Detection in Resources. For more information, see AWS Monitoring Setup and Adding Microsoft Azure Cloud Monitoring.

Cost exports from Azure now capture non-partitioned data. Previously, only partitioned cost export data that included manifest files was captured. This enhancement allows for ingestion of data without partitioning or manifest data present.

LogicMonitor now supports AWS Gateway Load Balancers. For more information on supported cloud resources, see Cloud Services and Resource Units.

Unable to convert normal collector group to auto balance collector group.

Autotask has stopped support for SOAP API. Hence, in Autotask integration, users will not be able to use SOAP API while creating a new Autotask integration. Use REST API for Alert Data in for your Autotask integration. When you create an Autotask integration with REST API, LogicMonitor provides default alert data. You can customize the alert data as per your need. For more information, see Autotask Integration in the product documentation.

For your existing Autotask integrations, to move from SOAP API to REST API, select Manage integration, select REST API option, and save the integration. You need to perform this step only once. After moving to REST API, it is not possible to move back to SOAP API. Selecting REST API option will not load existing customized XML alert data, but will provide default alert data and you can customise it as per your need. Before moving to REST API, if you need any support regarding your customized XML alert data, contact your Customer Support Manager.

To know more about Autotask end-of-lifecycle support for SOAP API, see SOAP API lifecycle FAQ from Autotask.

LogicMonitor now supports client_credentials grant type while using OAuth 2.0 in ServiceNow Integration. For more information, see ServiceNow (Incident Management) Integration in the product documentation

LogicMonitor now supports EKS and Bedrock logs for AWS log integration. For more information, see Sending AWS Logs in the product documentation.

The In operator has been removed from the Windows Event Logsource type. The In operator is no longer available to use to filter the Level attribute. For more information, see Windows Event Logging LogSource Configuration in the product documentation.

The updated Enhanced Script NetScan for Cisco Meraki adds support for collecting device model information using a new API endpoint.

For more information, see Cisco Meraki Monitoring in the product documentation.

The updated Enhanced Script NetScan for VMware SD-WAN validates that a serial number exists before adding the property to devices.

For more information, see VMware SD-WAN Monitoring in the product documentation.

The updated Enhanced Script NetScan for Palo Alto Prisma SD-WAN now supports filtering on serial number, site, and tags. For more information, see Palo Alto Prisma SD-WAN in the product documentation.

Moving forward, users must use the new Modules page to update core LogicModules, as the Import from Repository function is no longer available for this purpose.

For more information, see Modules Management in the product documentation.

Users can now edit LogicModule tags and preserve them when updating LogicModules.

For more information, see Modules Management in the product documentation.

In a future release, LogicModules will no longer be available from Settings. You can access the Exchange, My Module Toolbox, and all settings for managing modules from Modules in the navigation bar.

For more information, see Modules Overview 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 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. The released updated modules are listed in the LogicModules Release section.
  For more information, see LogicMonitor Provided Modules Groovy 4 Migration in the product documentation.

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.

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

java.lang.RuntimeException: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:

exception:groovy.lang.MissingPropertyException: No such property:

import com.santaba.agent.groovy.utils.GroovyScriptHelper 
import com.logicmonitor.mod.Snippets 
def modLoader = GroovyScriptHelper.getInstance(GroovySystem.version).getScript("Snippets", Snippets.getLoader()).withBinding(getBinding()) 

java.lang.RuntimeException: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed 

import groovy.util.XmlSlurper
import groovy.util.XmlParser
def xmlSlurper = new XmlSlurper()
def xmlParser = new XmlParser() 

import groovy.xml.XmlSlurper
import groovy.xml.XmlParser
def xmlSlurper = new XmlSlurper() 
def xmlParser = new XmlParser() 

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]

The LogicMonitor product documentation is now restructured to elevate the documentation that pertains to UIv4. The key updates are as follows:

• Improved Navigation—An intuitive structure that is product-centric to help you find the applicable information
• Updated Content Organization—Documentation is now grouped by UIv4 and Legacy UI documentation. All product documentation that pertains to the Legacy UI is collectively organized as “Legacy UI” content.
• Improved Search Capabilities—The documentation now has refined indexing for more precise results.

To access the product documentation, navigate to the Product Documentation landing page, and use the bookmarks panel to browse through the documentation.

You must enable the User Access permissions to run the reports and view existing reports.
To enable the access, navigate to Settings > User and Roles > Permissions > Reports.
For more information, see Reports Role Permissions in our product documentation.

Now, you can select these security recommendations and navigate to the screen where you can see the details.

• Remove LMV1 tokens associated with OOB Administrator role
• Remove Bearer Tokens associated to Users with OOB Administrator role
• Remove API tokens LMV1/Bearer tokens associated to the lmsupport support user
• Update your Windows Collectors to run as non-administrator
• Update your Linux Collectors to run as non-root

LogicMonitor displays all the recommended actions at the top of the Security page. For more information, see LogicMonitor Security Recommended Actions in the product documentation.