v.206 Release Notes

You can now enable two-factor authentication for Remote Session logins for better security by navigating to LogicMonitor portal > Settings > Portal Settings > Enabling Remote Session.

Note: Currently, the two-factor authentication is available only for local users.

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

For more information, see Initiating a Remote Session.

Users can filter resources in Resource Explorer by alert status using Alert Filters. Filter results by alert time, scheduled downtime, and using specific datapoints.

For more information, see Resource Explorer in product documentation.

Resource Explorer now automatically refreshes resource information while in Fullscreen.

This feature improves the function of Resource Explorer in Operation Center environments.

For more information, see Resource Explorer in product documentation.

Regions `ap-southeast-4` and `il-central-1` are now available for monitoring under AWS services. These regions correspond to Asia Pacific (Melbourne) and Israel (Tel Aviv).

You can now view resource data in Pie Charts and Donut Charts.

To access, navigate to Dashboards > Add Widget > Pie Chart > Display Settings > Visualization and select Donut Chart.

For more information, see the Pie Chart article in the product documentation.

Add a new Log Query widget to Dashboards. The Log Query widget provides log details that help you identify issues, errors, or anomalies within your IT infrastructure.

To configure the Log Query widget, navigate to Dashboards > Add Widgets > Logs.

For more information, see the Log Query Widget in our product documentation.

If you are using the Notes Updated HTTP method for your existing ServiceNow Incident Management Integrations, alert notes with the word “incident” in the ServiceNow table name or URL are not being sent to ServiceNow Work Notes.

A new method Dynamic Group Regex is added to WMI Logsource Log Fields. For more information, see Windows Event Logging Logsource Configuration in the product documentation.

A new method Dynamic Group Regex is added to Kubernetes pods and Kubernetes event logging Logsource Log Fields. For more information, see Kubernetes Event Logging LogSource Configuration and Kubernetes Pods LogSource Configuration in the product documentation.

The improved Enhanced Script NetScan for Cisco Meraki LogicModules now skips devices without a name or IP address to prevent the script from erroring out and failing to add any devices.

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

The improved Enhanced Script NetScan for Juniper Mist LogicModules now ensures that duplicate devices are not created without explicit consent using custom properties.

For more information, see Juniper Mist Monitoring 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 

In addition to setting static alert threshold, you can now set alert tuning parameters that include alert trigger interval, alert clear interval, and no data alert at the resource datasource level. While setting the static threshold, if you do not set the alert tuning parameters, the default values are applied. If you do not set static threshold and alert tuning parameters at the resource datasource level, then the static threshold and alert tuning parameters set at the resource group are applied. Currently, this feature is applicable only to DataSource Logic modules.

For more details, see Alerts Tuning Tab in the product documentation.

LogicMonitor v3 Python SDK now supports the return_raw_response property in all the GET calls. When you set the property value to True, the response only displays the specific result requested in the GET call. The new property avoids unrequested fields with 'null' value in the response. In addition, if a field label has an underscore for example, the created_by field, and you set return_raw_response=True then the value of created_by does not have an underscore in the response.

Similarly, LogicMonitor v3 GO SDK now supports two new methods in all the GET calls to display only the specific result that is requested in the GET call. For example, for Alerts the methods are // params := lm.NewGetAlertByIDJSONParams() and // resp, err := client.LM.GetAlertByIDJSON(params). The new methods avoid unrequested fields with 'null' value in the response.

The Datapoint Analysis feature is currently not supported for member instance graphs.

Node Grouping now supports Resource Groups, Resources, Alerts Page, and Alert Details.

For more information, see Node Grouping in our product documentation.

LogicMonitor has removed the API Only column from the All Users Table. This information is now available in the User Type column.

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

You can view the User Type column in the Legacy UI and New UI.