v.209 Release Notes

Windows Collectors can now run using non-administrator credentials. This provides you with improved security standards and mitigates the risk of unauthorized access and misuse within your installation environment.

Linux Collectors can now run using non-root credentials. This provides you with improved security standards and mitigates the risk of unauthorized access and misuse within your installation environment.

LogicMonitor has introduced Log Analysis, a new feature to LM Logs. It provides deeper insights using layered intelligence to summarize log data into visuals that aid in investigating and troubleshooting issues. It combines multiple criteria and dimensions to create a sentiment score for each log message, surfacing the most critical and impactful logs faster than ever. It also helps you to filter specific keywords and phrases to focus on the logs you want.

The updated Enhanced Script NetScan for Versa SD-WAN now excludes devices that do not provide asset information and no longer includes versa.organization in the folder structure when it is not set.

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

The improved Enhanced Script NetScan for JuniperMist LogicModules now adds debug support for CSV files that do not contain the Site Name of discovered resources.

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

The improved Enhanced Script NetScan for Cisco Meraki LogicModules now adds better defaults and null checks for MX IP address detection.

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

LogicMonitor officially supports Nutanix AOS 6.8, which is the latest release of the Nutanix Acropolis Operating System. LogicMonitor now supports Nutanix’s updated SNMP data profile and reference structure that was introduced in Nutanix AOS 6.8.

For more information, see Nutanix HyperConverged Infrastructure from the product documentation.

When selecting a module in the Exchange, you can now view all modules from your My Module Toolbox that are imported or cloned from that Exchange module under the Local Modules tab in the details panel. This view shows the name, description, version, status, and last updated date for each module. Selecting a module will take you directly to it in your toolbox.

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 Modules Management 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.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]

You can now add an instance group easily when moving an instance to the instance group.

Now while enabling two-factor authentication for a user, entering a phone number is non-mandatory.

For more information, see Users.

The LogicMonitor User Account notification emails sent during changes in First Name, Last Name, Password, Enable/Disable 2FA, Phone number, API Tokens, Email, or when a user status is manually changed to suspended, will now includes information regarding the user who performed the action, consisting of the following information:

• IP address
• Date & time
• LogicMonitor logo
• Copyright information with a privacy policy link for complete transparency

Using this feature, local users can add an authentication app-based verification as an additional layer of security for their accounts. Users can add any authentication app that adheres to the RFC standard, such as Okta, Google Authenticator, or Authy. Also, you could view list of users with 2FA enabled under Settings > User Access > Users and Roles > Users.

To enable 2FA app, go to Profile > Setup 2FA app.

For more information, see Two-factor Authentication App Access.

If your environment does not leverage Single Sign-On (SSO), all users with access to your LogicMonitor portal are required to use two-factor authentication (2FA) to access the portal. Leveraging 2FA provides you with stronger security measures to protect your account.

Using 2FA in your environment involves globally enabling 2FA in your LogicMonitor account and setting up 2FA account access using a third-party application, such as Authy.

To enable 2FA, navigate to Settings > Security Settings, and enable Require Two-Factor Authentication for all Roles and Users.

For more information about globally enabling 2FA for your LogicMonitor account, see Security Settings in the product documentation.

For more information about setting up 2FA with a third-party application, see Two-Factor Authentication Account Access in the product documentation.

For more information about LogicMonitor’s security mandates, see the Important Security Announcement in the LM Community.