v.206 Release Notes
Last updated on 17 June, 2024Account Information
Two-factor Authentication for Remote Session
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.
Cloud Monitoring
New Alert Filters Added to Resource Explorer
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 Supports Auto-Refresh in Fullscreen
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.
New monitoring for AWS Global Network
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).
Dashboards
Donut Chart Display Added to Pie Chart Widget
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.
Added Log Query Widget
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.
Integrations
Alert Notes
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.
LM Logs
Dynamic Group Regex for WMI Logsource Log Fields
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.
Dynamic Group Regex method for Kubernetes Pods and Kubernetes Event Logging LogSource Log Fields
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.
Modules
Improved Cisco Meraki NetScan
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.
Improved Juniper Mist NetScan
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.
LogicModules Migrating to Modules
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.
Apache Groovy 4 Support for all LogicMonitor-Provided LogicModules
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.
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.
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, 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, 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]
Important: 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, the following exception is thrown:
exception:groovy.lang.RunTimeException: Unable to load FastStringService
Resources
Addition of Alert Tuning Parameters at Resource Datasource Level
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.
REST API
Updates to Python and GO v3 SDK Response
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.
Service Insights
Datapoint Analysis Feature
The Datapoint Analysis feature is currently not supported for member instance graphs.
Topology
Enhanced Node Grouping
Node Grouping now supports Resource Groups, Resources, Alerts Page, and Alert Details.
For more information, see Node Grouping in our product documentation.
User Access
API Only Column Removed From All Users Table
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.
Collector Releases
EA Collector 35.401 was released on May 22, 2024. For more information, see the EA Collector 35.401 Release Notes.
Container Monitoring Releases
Container Monitoring 7.1.1 was released on May 28, 2024. For more information on new Container Monitoring features, enhancements, fixed and known issues, and the upgrade steps, see Container Monitoring 7.1.1 Release Notes.
LogicModule Releases
New and updated LogicModules are available for you directly in your LogicMonitor portal. You can install new modules from the Exchange and update existing modules in My Module Toolbox. For more information, see Modules Installation and Modules Management in the product documentation.
This section lists the LogicModules that are new in this release, updated in this release, or will be removed in a future release.
Updated LogicModules
Updated LogicModules | Details |
1 DataSources: – Cisco_Catalyst_AccessPointHealth | Revised the status alert evaluation to greater than 1, instead of values below 1. |
3 ConfigSources: – SCP_Standard – SFTP_Standard – SSH_Exec_Standard | All Common Configs now clear alerts on Acknowledgement. |
1 DataSources: – Cisco_NTP 1 PropertySources: – addCategory_CiscoNTP 2 LogSources: – Meraki Network Events – Meraki Security Appliance Events | Updated Cisco NTP modules that use SSH are now much more careful with resource usage. This should prevent large CPU spikes when running on some devices. Updated Meraki LogSources now ignore duplicate log entries, and perform notably better. |
5 DataSources: – Cisco_Meraki_API – Cisco_Meraki_AccessPointSSIDs – Cisco_Meraki_SecurityApplianceHealth – Cisco_Meraki_SecurityApplianceTunnels – Cisco_Meraki_SecurityApplianceUnderlay 1 PropertySources: – addERI_Cisco_Meraki_Device 1 LogSources: – Meraki Network Events | To avoid complications arising from a network ID update without a subsequent NetScan rerun, modules now default to ‘auto.meraki.networkid’. |
1 DataSources: – Cisco_Meraki_AccessPointHealth | Fixed an issue that caused the fallback value to not be reported when status is null. |
1 DataSources: – Microsoft_SQLServer_MonitorUser | Corrected a typo and correctly exclude devices with the system category “SQL_Node”. Warning: Dataloss is possible for SQL cluster node resources that were collecting this data, however these devices are not intended for this module. |
2 PropertySources: – ConfigCheck_4_Interactive – ConfigCheck_5_Telnet | Fixed an issue in Common Config interactive PropertySource where a config larger than the set limits would cause a failure preventing subsequent configs being checked. |
1 DataSources: – Docker_Containers_cAdvisor20 | Updated description of status datapoint and removed alerts. |
1 DataSources: – VMware_ESXi_NetworkInterfaces 1 TopologySources: – Networking_L2_snmpSwitch | Added interface ERI. Added support for topo.bridgetables host property to process bridge tables even when discovering LLDP/CDP neighbors. |
1 DataSources: – VMware_SDWAN_Interfaces | Fixed an issue with the link ID lookup fallback method that caused AD and collection to fail. |
2 PropertySources: – NetApp_System_Info – addCategory_Cisco_ISE_MNT | Updated to support compatibility with Groovy 2 and Groovy 4. Added import of a new JPMS compliant package to continue support of XMLParser. |
4 PropertySources: – addCategory_CiscoCUCMAPI – addCategory_EMC_Avamar – addCategory_NetApp – addERI_NetApp | Updated to support compatibility with Groovy 2 and Groovy 4. Added import of a new JPMS compliant package to continue support of XMLSlurper. |
1 LogSources: – Cisco_Catalyst_Center_Issues | Removed “Error:” from message field of logs that was capturing redundant data. |
1 DataSources: – Cisco_Catalyst_SDWAN_API 1 LogSources: – Cisco Catalyst SDWAN Alarms | Improved performance of Cisco Catalyst SDWAN Alarms. |