v.205 Release Notes

As of this release, A company portal admin can now choose to display the Keep Me Signed In option on the LogicMonitor portal login page. Secondly, for the users who select the Keep Me Signed In option while logging in, the admin can now configure the Keep Me Signed In days limit settings to keep their user session active for a certain number of days.

For the new customers, the Keep Me Signed In session timeout duration is 30 days, whereas for the existing customers it is 0 days. The value 0 days indicates no restriction, implying that there is no timeout to ensure the existing behaviour is unaffected. The new users can also set the timeout value to 0 days in the account settings. For more information, see Portal Settings in the product documentation.

As of this release, user session timeout can be set to as low as 15 minutes. A user session inactive for a specified time will result in a user being logged out. The timeout period is applied to users who do not enable the Keep Me Signed In option when they log into their LogicMonitor portal.

To access this, go to Settings > Account Information > Portal Settings. For more information, see Portal Settings in the product documentation.

The password assistance notification emails now includes information regarding the user who performed the action, IP address, time & date, LogicMonitor logo, and a privacy policy link for complete transparency.

LogicMonitor has added the User Type column to the All Users table (Settings > Users and Roles > Users). The User Type column displays three types of users: SAML, Local, and API only.

LogicMonitor has also added the User Type filter to filter users of a specific user type. On the UIv4, you can both view the User Type column and use the User Type filter. However on the UIv3, you can only view the User Type column. The User Type filter is not available in UIv3.

LogicMonitor has added a new column ServiceNow incident to the Alerts page. It contains link to ServiceNow incident tickets. You can select the link to directly open the incident ticket in the ServiceNow portal. For more information, see ServiceNow (Incident Management) Integration in the product documentation.

You can now use Notes updated HTTP delivery method from the LogicMonitor ServiceNow integration to update the Work notes section of the incident in ServiceNow. For more information, see ServiceNow (Incident Management) Integration in the product documentation.

Fixed an issue where alerts were not delivered to the unverified admin email addresses added by customers to the custom email integration in the escalation chain. LogicMonitor now verifies the admin email addresses that are added to the escalation chain. Users will now receive a verification email to verify their unverified admin email address whenever their admin email address is added to a new or an existing escalation chain.

Now when you select a deprecated module, there may be a recommendation for a replacement module. You can check if a module is deprecated by looking under the support column or in basic information and origin status of the module, where the replacement recommendation appears.

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 with the groovy4 tag, as available
  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 

LogicMonitor has added Resource DataSource level threshold support for static and dynamic datapoints. If the instances and their parent instance groups do not have their own defined thresholds, they inherit the threshold set at their resource datasource level. The threshold is applicable only to multi instance resource datasource. For more information, see Enabling Dynamic Thresholds for Datapoints and Tuning Static Thresholds for Datapoints in the product documentation.

Note: You can create, update, and delete thresholds only on the LogicMonitor UIv4 portal. The LogicMonitor UIv3 portal allows you to only view the thresholds.

You can now focus on any group, device, or cloud resource. When you select the icon, the Resource Tree focuses only on the selected resource. This feature aims to streamline navigation and improve accessibility by allowing you to delve deeper into specific content or elements.

For more information, see Navigating the Resources Page (New UI) in the product documentation.