v.208 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.

You can use a prompt-based wizard to complete this migration.

To leverage the enhanced security, you need EA Collector 35.400 or later installed. For more information see the EA Collector 35.400 Release Notes.

For more information, see the following in the product documentation:

• Migrating Windows Collector from Admin to Non-admin User
• Credentials for Accessing Remote Windows Computers
• Windows Server Monitoring and Principle of Least Privilege

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

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.

You can use either a prompt-based wizard or a silent migration process to complete this migration.

To leverage the enhanced security, you need Collector GD 36.000 or later installed. For more information, see the GD Collector 36.000 Release Notes.

For more information, see the following in the product documentation:

• Migrating Collector from Root to Non-root User
• Installing Collectors

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

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.

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]

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

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 runtime 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. If you are leveraging customized or community-provided modules, you must update the module to pass valid parameters into all data structures.

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

Important: LogicMonitor is releasing updates to LogicModules to mitigate this issue for official LogicMonitor-provided modules. If you are leveraging customized or community-provided modules, you must update the module to pass valid parameters into all data structures.

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:

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

For example, the following demonstrates how GroovyScriptHelper is used in Groovy 2:

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"

You can modify the script to use the GroovyScriptHelper in Groovy 4, demonstrated in the following:

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"

Important: LogicMonitor is releasing updates to official LogicModules to mitigate this issue for LogicMonitor-provided modules. If you are leveraging customized or community-provided modules, you must update the module to pass valid parameters into all data structures.

The Scan History tab now displays the Resource Status column. You can now view the resource status information for NetScans. To view the status, navigate to Settings > NetScans > select the required NetScans > Scan History > Resource Status.

For more information, see the Viewing Resource Status Information article in our product documentation.

The term Alert Generation is now called Alerting. When enabling or disabling alerts for datapoints, select Disable Alerting  or Enable Alerting from the alert tuning tab.

For more information, see the Alerts Tuning Tab (New UI) from product documentation.

In this release, we have added POST /setting/accessgroup/mapunmap/modules endpoint to the Access Group API. You can use this endpoint to provide details of one or multiple Logic Modules and access groups for mapping or unmapping. For more information, see REST API v3 Swagger Documentation.

The ability to create API tokens is now restricted to users who are not lmsupport, along with users who do not have the Administrator role. This restriction prevents unauthorized access and potential misuse of elevated permissions, ensuring that API keys are generated and managed within a controlled and secure framework.

As a result of this restriction, you must migrate any previously created API tokens assigned to the LMSupport user or a user with the Administrator role to a new API token assigned to a new user and role with appropriate permissions.

To access this, navigate to Settings > Users and Roles > select the LMv1 API Token tab and add a new token.

For more information, see API Tokens.

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

To improve security, you can now enable two-factor authentication for remote session logins for SAML users by navigating to LogicMonitor portal > Settings > Account Information > Portal Settings > Enabling Remote Session.

Note: When Require Two-Factor Authentication for Remote Session is enabled in Portal Settings for a local user, SAML users will be directed to do a 2FA remote session too.

To access the remote session, navigate to Resource Tree > Manage Resource Options > Start Remote Session.

For more information, see Initiating a Remote Session.

LogicMonitor has dropped the Tenant Name and Tenant Domain fields from the Single Sign-On configuration. However, these fields are mandatory when you configure multi-SSO.

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.