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

Cost Optimization Billing and Recommendations are now available as a new monitoring product. Monitor costs associated with your cloud environments, and get detailed recommendations for optimizing your resources and the associated costs.

For more information on purchasing Cost Optimization, see https://www.logicmonitor.com/pricing. For details on Billing monitoring and Recommendations, see Cost Optimization – Billing and Cost Optimization – Recommendations.

Use this HTTP delivery method to update the Work notes section of the incident in ServiceNow

If the HTTP URL and HTTP method of the Notes updated section of your existing ServiceNow integration is blank, use your existing working configuration of Active HTTP delivery options to update the configuration. Use the following token configuration for alert data for the Notes updated HTTP delivery method:

{   “number”: “##EXTERNALTICKETID##”,   “logicmonitor_alert_id”: “##ALERTID##”,   “work_notes”: “##ALERT_NOTE##” }

For more information, see ServiceNow (Incident Management) Integration in the product documentation.

The improved Enhanced Script NetScan for Cisco Meraki LogicModules now adds support for meraki.api.key.addToAllDevices, which if set to false prevents the Meraki NetScan from adding the meraki.api.key property to newly added resources.

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

Meraki Assurance Alerts LogicSource is available for Cisco Meraki Monitoring. In addition, new optional Meraki properties meraki.api.key.addToAllDevices, meraki.disable.network.events, meraki.disable.security.events, and meraki.disable.assurance.alerts are available.

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

LogicModules are no longer 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 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]

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

In this release, we have added the accessGroups and accessGroupIds fields to LogicMonitor REST API v3.

You can find the accessGroups and accessGroupIds in the request of the following API endpoints:

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 or Bearer Tokens tab accordingly.

For more information, see API Tokens.

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

You can now automatically disable tokens after a set number of days of inactivity. This helps mitigate risks related to the disclosure of previously generated and unused LMv1, Bearer, and Widget Tokens. By default, for all new accounts, the option is set to 365 days, and for all the existing accounts it is set to 0 days. Admin users with Manage Security permission can set the number of inactive days.
To access this feature, navigate to Settings > Security Settings, and set the number of inactive days for the Disable Tokens (LMv1, Bearer, Widget) after _ days of inactivity option.
For more information, see LMv1, Bearer, and Widget tokens product documentation.

The LogicMonitor Security Code notification emails sent during Two-factor Authentication login and password reset now include information regarding the user who performed the action, IP address, time & date, LogicMonitor logo, and a privacy policy link for complete transparency.

You can now control all the settings related to security for your LogicMonitor portal from a single location. The new Security page provides the latest recommendations for configuring and securing your portal. All the authentication-related settings and other critical settings (for example, remote session and test script) from the Portal Settings page are now moved to the new Security page.

You must have a LogicMonitor user with the new Security permission set to configure the Security settings. This permission set is available when you add a role from Settings> Users and Roles > Add Role. For more information, see Adding a Role.
This permission is cloned from the existing Account Information permissions.

To access this feature, navigate to Settings> Security.

For more information, see Security Settings in the product documentation.

LogicMonitor OpenTelemetry Collector (lmotel) is updated to version 4.0.00 for application performance monitoring. This release includes the following updates:

• LogicMonitor now uses OpenTelemetry Collector Contrib version 0.95.0. For more information, see OpenTelemetry Collector Contrib version 0.95.0 from OpenTelemetry.
• Added support for proxy
• Added loadbalancingexporter and debugexporter. For more information, see loadbalencingexporter and debugexporter from GitHub.
• Removed the support for ballastextension

For more information, see OpenTelemetry Collector Versions in the product documentation.

You can now provide users with granular control of modules using Access Groups. This allows you to enable specific users with access to a module, providing you with more granular control of the users that have access and the level of access to the modules in My Module Toolbox. For example, you can create an Access Group that allows users to create a module but not commit the module. You could also prevent users from editing specific fields.

You can also remove Access Groups from modules as necessary. Removing an Access Group from a module completely removes access to that module for the users associated with the Access Group.

To set up this feature, you must create the Access Group and then configure the user access with the Access Group. To set up Access Groups, navigate to Settings > Users and Roles. For more information, see Access Groups Settings and Modules Role Permissions in the product documentation.

To leverage this feature in Modules, navigate to Modules > My Module Toolbox and add or edit a module. The settings for Access Groups are displayed in the module editor. For more information, see Access Groups for Modules in the product documentation.

If any changes are made to portal settings, an email notification is sent to the primary contact and all the additional contacts mentioned in the portal. In addition, if the Require Two-FactorAuthentication for all Roles and Users option is enabled or disabled, an email notification is sent to all local users along with primary and additional contacts.

To view the settings, navigate to Settings > Account Information > Portal Settings.

For more information, see the Portal Settings article in the product documentation.

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.