v.210 Release Notes

Widgets for Resource Explorer now reflect filter properties applied in the Resource Explorer dashboard.

If a widget filter property is the same as the property in the Resource Explorer dashboard, the values in the dashboard property filter will override those of the widget.

After integrating Microsoft Teams with Custom HTTP integration, when you test the alert delivery, the test alert is delivered to the configured MS Teams channel. However, a message Timeout Received Waiting for HTTP Response is displayed while testing the alert delivery.

Enhanced Script NetScan for Juniper Mist now properly handles mist.api.org.collector.sites.csv when provided.

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

Enhanced Script NetScan for Cisco Catalyst Center now excludes devices without a display name.

For more information, see Cisco Catalyst Center 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.

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.

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

if(GroovySystem.version.startsWith("2.")) {
    modLoader = com.logicmonitor.common.sse.utils.GroovyScriptHelper.getInstance()._getScript("Snippets", Snippets.getLoader())
} else {{{}}
    modLoader = com.santaba.agent.groovy.utils.GroovyScriptHelper.getInstance("v4").getScript("Snippets", Snippets.getLoader())
} 

import com.logicmonitor.common.sse.utils.GroovyScriptHelper as GSH
import com.logicmonitor.mod.Snippets 
 
modLoader = GSH.getInstance()._getScript("Snippets", Snippets.getLoader()).withBinding(getBinding()) 
 
lmDebug = modLoader.load("lm.debug", "0", true) 
lmDebug.default_context = "Test:SettingContext"

import com.logicmonitor.mod.Snippets 
 
if(GroovySystem.version.startsWith("2.")) {    
modLoader = com.logicmonitor.common.sse.utils.GroovyScriptHelper.getInstance()._getScript("Snippets", Snippets.getLoader())
} else {   
modLoader = com.santaba.agent.groovy.utils.GroovyScriptHelper.getInstance("v4").getScript("Snippets", Snippets.getLoader())
} 
 
lmDebug = modLoader.load("lm.debug", "0", true) 
lmDebug.default_context = "Test:SettingContext"

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

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

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]

LogicMonitor has now updated LogicMonitor REST API v3 Swagger, v3 Python, and GO SDK files with new endpoints. You can find API endpoints added to the new categories: ConfigSources, EventSources, JobMonitor, OID, PropertySource, and Topology. In addition, LogicMonitor has also updated some existing categories with new endpoints. For more information, see REST API Change Log and REST API v3 Swagger Documentation. The Swagger and SDK files will be available after the v210 deployment to production is complete. For any questions, contact your LogicMonitor Customer Success Manager.

We have added the following security recommendations for configuring and securing your portal.

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

To access this feature, navigate to Settings > Security.

For more information, see LogicMonitor Security Recommended Actions in the product documentation.

The two-factor Authentication push approval function is disabled as we no longer use the deprecated Authy API. We may consider reintroducing a similar function in a future release. For more information on available 2FA options such as TOTP, see Two-Factor Authentication Account Access in the product documentation.

To enhance clarity and performance, topologies exceeding 500 nodes will be automatically grouped by resource type. Multiple edges between nodes will be represented by a single aggregate edge.
For more information, see Node Grouping in our support documentation.

With this release, the topology map will no longer support undiscovered vertices. This feature is deprecated to improve overall performance.

LogicMonitor now performs probabilistic sampling when you ingest traces through the REST API. The default sampling ratio is 0.1 of the total traces. For example, if you ingest 1000 traces through the REST API, approximately 100 traces are sampled and visible on your LogicMonitor portal.

LogicMonitor OpenTelemetry Collector (lmotel) is updated to version 5.0.00 for application performance monitoring. LogicMonitor now enables you to upgrade your OpenTelemetry Collectors.
For more information, see OpenTelemetry Collector Versions in the product documentation.

To perform the create, read, update, and delete (CRUD) operations for access group and to map or unmap modules with access group, previously, LogicMonitor supported a combined option Manage Access Groups. It was placed under Users and Roles > Roles > Manage > Permissions > Modules > Manage Access Groups. For better granular access control, LogicMonitor has now separated the actions and added two options.

• The Access Groups option—Enables you to perform the CRUD operations for access group permission. To access the option, navigate to Users and Roles > Roles > Manage > Permissions > Settings > Access Groups.
• The Map and unmap Modules to Access Groups option—Enables you to map or unmap LM Module with the existing access groups. To access the option, navigate to Users and Roles > Roles > Manage > Permissions > Modules > Map and unmap Modules to Access Groups.
  For more information, see Settings Permissions and Configuring Modules Permissions in the product documentation.