v.209 Release Notes

Last updated on 20 August, 2024

Feature Highlights

  • Added Log Analysis feature in LM Logs
  • Enhanced LogicMonitor User Account Change Notification
  • Enable an Authentication App as an option for Two-Factor Authentication

Monitoring Updates

  • Improved Juniper Mist NetScan and Cisco Meraki NetScan LogicModules
  • Nutanix AOS 6.8 OS Officially Supported
  • New Local Modules Tab Added to LM Exchange
  • Added new monitoring for Cato SD-WAN GraphQL API-based monitoring of Cato Sockets
  • Updated Cisco_Catalyst_SDWAN modules

Collector Settings

Security Upgrade

Windows Collectors Least Privilege

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.

Warning: As a result of this security enhancement, you must migrate all Windows Collectors to run as non-admin.

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:

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

Security Upgrade

Linux Collectors Least Privilege

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.

Warning: As a result of this security enhancement, you must migrate all Linux Collectors to run as non-root users.

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:

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

LM Logs

Enhancement

Added Log Analysis feature to LM Logs

LogicMonitor has introduced Log Analysis, a new feature to LM Logs. It provides deeper insights using layered intelligence to summarize log data into visuals that aid in investigating and troubleshooting issues. It combines multiple criteria and dimensions to create a sentiment score for each log message, surfacing the most critical and impactful logs faster than ever. It also helps you to filter specific keywords and phrases to focus on the logs you want.

Modules

Enhancement

Improved Versa SD-WAN NetScan

The updated Enhanced Script NetScan for Versa SD-WAN now excludes devices that do not provide asset information and no longer includes versa.organization in the folder structure when it is not set.

For more information, see Versa SD-WAN Monitoring in the product documentation.

Enhancement

Improved Juniper Mist NetScan

The improved Enhanced Script NetScan for JuniperMist LogicModules now adds debug support for CSV files that do not contain the Site Name of discovered resources.

For more information, see Juniper Mist Monitoring from the product documentation.

Enhancement

Improved Cisco Meraki NetScan

The improved Enhanced Script NetScan for Cisco Meraki LogicModules now adds better defaults and null checks for MX IP address detection.

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

Enhancement

Nutanix AOS 6.8 OS Officially Supported

LogicMonitor officially supports Nutanix AOS 6.8, which is the latest release of the Nutanix Acropolis Operating System. LogicMonitor now supports Nutanix’s updated SNMP data profile and reference structure that was introduced in Nutanix AOS 6.8.

For more information, see Nutanix HyperConverged Infrastructure from the product documentation.

Enhancement

New Local Modules Tab Added to LM Exchange

When selecting a module in the Exchange, you can now view all modules from your My Module Toolbox that are imported or cloned from that Exchange module under the Local Modules tab in the details panel. This view shows the name, description, version, status, and last updated date for each module. Selecting a module will take you directly to it in your toolbox.

For more information, see Modules Overview in the product documentation.

Deprecation

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

Known Issue

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.

Known Issue

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.

Known Issue

When running a module using Apache Groovy 4, and using java.util.Date.format(), the following exception is thrown:

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.

Known Issue

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

Resources

Enhancement

You can now add an instance group easily when moving an instance to the instance group.

Security Settings

Enhancement

Phone Number Field Non-mandatory for Two-Factor Authentication

Now while enabling two-factor authentication for a user, entering a phone number is non-mandatory.

For more information, see Users.

Enhancement

Enhanced LogicMonitor User Account Change Notification

The LogicMonitor User Account notification emails sent during changes in First Name, Last Name, Password, Enable/Disable 2FA, Phone number, API Tokens, Email, or when a user status is manually changed to suspended, will now includes information regarding the user who performed the action, consisting of the following information:

  • IP address
  • Date & time
  • LogicMonitor logo
  • Copyright information with a privacy policy link for complete transparency
Enhancement

Enable an Authentication App as an option for Two-Factor Authentication

Using this feature, local users can add an authentication app-based verification as an additional layer of security for their accounts. Users can add any authentication app that adheres to the RFC standard, such as Okta, Google Authenticator, or Authy. Also, you could view list of users with 2FA enabled under Settings > User Access > Users and Roles > Users.

To enable 2FA app, go to Profile > Setup 2FA app.

For more information, see Two-factor Authentication App Access.

User Access

Security Upgrade

Required Two-Factor Authentication for all Users

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.

Container Monitoring Releases

Container Monitoring 8.1.0 was released on July 09, 2024. For more information on new Container Monitoring features, enhancements, fixed and known issues, and the upgrade steps, see Container Monitoring 8.1.0 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. Changes related to the LogicModule feature will be listed in the General Updates section.

New LogicModules

LogicModule NameDetails
4 DataSources:
  – Cato_SDWAN_API
  – Cato_SDWAN_Health
  – Cato_SDWAN_Interfaces
  – Cato_SDWAN_Tunnels
2 PropertySources:
  – addCategory_Cato_SDWAN
  – addERI_Cato_SDWAN
New monitoring for Cato SD-WAN GraphQL API-based monitoring of Cato Sockets.

Updated LogicModules

LogicModule NameDetails
2 PropertySources:
  – addCategory_Juniper_Mist_Device
  – addERI_Juniper_Mist_Device
Updated tech notes to mention requirement of Juniper_Mist_API DataSource.
1 PropertySources:
  – addCategory_Juniper_Mist_Device
1 TopologySources:
  – Juniper_Mist_Topology
Changed the Elect first org site device not first site device for topology observer and allow for custom prop mist.topology.observer for topology source applies to when first mist org site is not added to monitoring use case.
2 DataSources:
  – Juniper_Mist_SDWAN_Edge_Health
  – Juniper_Mist_SDWAN_Edge_Performance
Changed allow for Mist SDWAN devices to be identified by system.hostname IP addresses.
1 DataSources:
  – CommVault_Windows_Services
Updated filter to check for instances based on name instead of display name.
1 PropertySources:
  – Device_BasicInfo
Added handling for Cisco Firepower devices.
1 PropertySources:
  – addCategory_Juniper_Mist_Device
Removed “NoPing” from system.categories for APs. Note: this property must be removed from existing devices manually since system.categories are not removed by PropertySources.
1 PropertySources:
  – ConfigCheck_5_Telnet
2 ConfigSources:
  – Telnet_Interactive_Dynamic
  – Telnet_Interactive_Standard
Changed Telnet Common Configs now support situations where IAC request data was mixing with authentication lines.
Updated
1 DataSources:
  – HP_MSA_GlobalStatus
Changed the textmatch for Status datapoint to look for “OK” in the output instead of “: OK”
1 DataSources:
  – CommVault_ManagementConsole
Added check for backslash in the username.
1 PropertySources:
  – Config_Arista_Generic
Common Configs now attempt to avoid pagination on Arista EOS.
1 DataSources:
  – Cisco_Meraki_API
Added validation to eliminate unnecessary per network API calls when no Security Appliances are being monitored.
1 LogSources:
  – Cisco Catalyst SDWAN Alarms
Updated to map log severity to the Log Level field.
1 DataSources:
  – Win2k12_HyperV_HypervisorStats
Added functionality to accurately determine the count when memory statistics are represented as PSCustomObject.
Updated
1 DataSources:
  – LogicMonitor_ConfigSource_Metrics
3 PropertySources:
  – ConfigCheck_1_SFTP
  – ConfigCheck_2_SCP
  – ConfigCheck_3_Exec
6 ConfigSources:
  – SCP_Dynamic
  – SCP_Standard
  – SFTP_Dynamic
  – SFTP_Standard
  – SSH_Exec_Dynamic
Changed SFTP, SCP, and EXEC Common Configs now use the same authentication, logging and general processing.
Updated
8 DataSources:
  – Cisco_Catalyst_SDWAN_API
  – Cisco_Catalyst_SDWAN_ControlConnections
  – Cisco_Catalyst_SDWAN_ControllerHealth
  – Cisco_Catalyst_SDWAN_ControllerInterfaces
  – Cisco_Catalyst_SDWAN_DeviceHealth
  – Cisco_Catalyst_SDWAN_NetworkInterfaces
  – Cisco_Catalyst_SDWAN_Performance
  – Cisco_Catalyst_SDWAN_Tunnels
1 PropertySources:
  – addCategory_Cisco_Catalyst_SDWAN
Changed resolved issue causing only a single network interface to be reported. Added support for the option to display all network interfaces by setting the property “cisco.sdwan.interfaces.all” to true. Controller and Network interfaces will now be discovered regardless of the state to keep alerts active if an instance goes down. Additional general improvements.

Note: If the API module is updated all modules in the package will need to be updated or collection will break.