LogicMonitor v.193 is scheduled to roll out to customer portals from October 2, 2023 through October 9, 2023.
New Modules for Cisco Meraki Monitoring
You can now leverage the device-based modules that support Meraki Dashboard API 1.36 (current version). LogicMonitor provides a new Enhanced Script NetScan to automate discovering and onboarding Meraki Security Appliance, Switch, Wireless Access Point, and Smart Camera devices and to automatically organize the Resources in Groups by Meraki Organization and Network name. These modules introduce new features, an intuitive user experience, simplified ServiceNow CMDB Integration, and support for core LM Envision features like Network Traffic Analysis, Log Analysis, and Role Based Access Control.
Enhancements to the Module Update Workflow
You can now view and preserve changes prior to finalizing a module update. This allows you to view the changes in a side-by-side data comparison view of the module configurations and preserve the AppliesTo and Alert Thresholds values before the Final Review page when updating a module. In addition, you can now enable a three panel viewer that allows you to view the following information in separate panels regarding the module configuration update:
- Currently installed module
- Upgraded module
- Resulting module after upgrading
To access this feature, navigate to Modules > My Module Toolbox > select Update for the Module you want to update. You can choose the preservations you want to persist with the update in the Preservations panel, and you can enable the three panel view by toggling the Display three panel view switch.
For more information, see “Installing a Module Update” in Modules Management in the product documentation.
New Roles for My Module Toolbox and Exchange
Disclaimer: This feature is currently only available if you have access to the new UI preview. To gain access, contact Customer Success.
LogicMonitor now has separate roles for My Module Toolbox and Exchange, allowing you to assign these roles to a user. Previously, the Toolbox and LM Exchange shared a single set of permissions, and “Manage” was required to view the Exchange.
The Exchange role now allows you to delegate “Commit” and “Publish” rights to the Exchange in addition to the standard “View” and “Manage” permissions. This provides you with additional control over what users can commit private or publish version of modules in your LogicMonitor portal.
To access these features, navigate to Settings > Users and Roles, and select the Roles tab.
For more information, see Roles in the product documentation.
Enhancements to Topology Maps
When creating and exploring Topology Maps, you can now search for nodes faster and save filters for your connections:
- Search Nodes–To help you find nodes faster (on very large maps, for instance), you can now search for nodes in the maps by their label names. For more information, see Searching for Nodes.
- Saving Connections Filter in Maps–You can now set a filter for connections, and save the view for later in the saved maps. For more information, see Saving Connections Filter in Maps.
To access these features, navigate to Mappings > Saved Maps.
Application Performance Monitoring
- Any Push Metrics instance that has not received data for the last 45 days and is dormant will be automatically deleted. For more information, see Managing DataSources Created by the Push Metrics API in the product documentation.
- When configuring alert conditions and alert pipelines for Logs, the description field is no longer a mandatory field.
- SNMP SysOID Edit page now displays version information, similar to other module types.
- Fixed an issue that caused data to be omitted from audit logs after a module was updated from the Exchange. This can result in missing values in the Audit Logs if a module was upgraded prior to v193.
- Added a new icon for security cameras in Topology Maps.
Disclaimer: The new UI preview is currently in Beta. In the coming weeks, this beta will be made available for all users. For more information, see New UI Overview in the product documentation. To gain access to the new UI preview, contact Customer Success.
- Instance name is now available on the alert tuning tab for multi-instance datasources so it’s now easier to identify which datapoint ties to which instance.
- In the Resources Info tab, the Inherited from column now links to the correct Resource, Resource Group, or PropertySource.
- For parity with the legacy UI for Resources:
- Additional filters will now be appended to statements as “OR” operations.
- When manually adding a new instance, you will see the default “Ungrouped” instance group automatically populated in the field.
GD Collector 33.007 will be designated as the MGD collector on October 6, 2023. Any collectors having versions below GD 33.007 on November 6, 2023 will be forcefully updated to GD 33.007. For more information, see our MGD policy in the product documentation.
Container Monitoring Releases
Container Monitoring 5.0.0 was released on September 18, 2023. For more information on new Container Monitoring features, enhancements, fixed and known issues, and the upgrade steps, see Container Monitoring 5.0.0 Release Notes.
New and updated LogicModules are available for you to import from the LogicMonitor Public Repository. 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 modules for monitoring Cisco Meraki-managed devices as discrete resources in LogicMonitor This package leverages the Dashboard API and snmp.meraki.com to monitor Cisco Meraki-managed devices. The modules in this package apply to LM Envision resources that represent discrete Meraki devices. These modules are not in-place upgrades from legacy Meraki modules that applied to LM Envision resources which represent a Meraki Org or Meraki Network.|
For more information about migration from legacy modules and onboarding of discrete Meraki devices, see Cisco Meraki Monitoring in the product documentation.
|New modules for monitoring Oracle MySQL connections. Has the ability to run custom SQL queries and report the round trip time to completion for the query. Will alert if connection problems occur.|
|Added checks for successful connections. If the connection fails it will try for 20 seconds to establish one. After that it gives up. Writes a marker file so the collector will know the previous attempt failed to prevent from attempting to log onto servers to many times.|
Updated all ActiveDirectory Configs with new session handling.
|Long-term logging for config diagnostics are now maintained permanently in /logs/ConfigStats/ directory when the host property config.logs.permanent is set to 1 or true.|
Note: These logs are never removed automatically, so use this setting sparingly for diagnostics.
|Add support for 18.104.22.168.4.1.322.214.171.124.10.2.2.1.3 wildvalue/alias discovery and 126.96.36.199.4.1.3188.8.131.52.10.2.2.1.8 temperature readings if the default OIDs return empty results|
|Added check for response before attempting to create instances. Updated snippet code for Cisco DNAC LogicModules to account for version 1.2.6 or below login URL.|
|Add null check for network ILP before attempting to set.|
|Changed the type of the following metrics. They were derive, and were corrected to gauge: BlockedByFireWall, ConnectionFailed, ConnectionSuccessful, Deadlocks.|
|Changed the type of a few metrics.|
|Expanded the system database list. To fix performance issues, changed collect on databasestorage to skip system databases if the msql.excludesystem.database = true. Prior code executed the queries on the system databases and have the output filtered by active discovery instances. Fixed issues with SQL 2012 SP1 not returning a major version number. Cleaned up some coding issues.|
|Added support for NetApp ONTAP REST API starting in version 3.0 of NetApp_Cluster_ modules. Updates are backwards compatible and will not impact historical data upon importing. Additional modules are available for validation testing; contact your CSM for more information.|
Providing default property values in case DataSources are updated prior to importing updated PropertySource.
Updated NetApp_Cluster_GlobalPerformance to handleZAPI to reflect v1.5.0 Active Discovery method.
|Corrected token in alert body on DaysRemaining datapoint.|
|Corrected isMac() function call to correctly reference debug variable.|
|Updated the logging and debugging function of the vSphere suite to use the lm.debug snippet and removed unnecessary runAfterLoad argument for the vmware.vsphere snippet to prevent issues with initial loading of snippets in new accounts.|
Updated VMware_vSphere_DatastoreStatus to add missing overallStatusMap.
Updated VMware_vSphere_VirtualMachineStatus to fix formatting of collection output.
|Added support for Aruba JL728A Devices to common configs.|
|Where applicable, SFTP and SCP Common Configs now use the LogicMonitor tmp directory for intermediate caching of downloading configs.|
|Added support for new optional property that increases the timeout for OID associated with endpoint.model on Cisco devices. Setting deviceBasicInfo.useLongerTimeout.enable=true on Cisco devices will increase the time for walking OID 184.108.40.206.220.127.116.11.18.104.22.168 from 30 seconds to 120 seconds in an attempt to avoid the fallback to 22.214.171.124.126.96.36.199.0.|
|Fixed bug on version property for servers with multiple SQL instances that caused truncation of instances. Added filtering for non-clustered servers to make sure the instance name matches the assigned instance name. No longer checks the server for matching Instance name when there are manual instances.|
This table lists LogicModules that we are deprecating in this release. This means that these LogicModules will be removed in a future release. If available, a replacement LogicModule is listed. For the history of deprecated modules, see Deprecated LogicModules.
|LogicModule Deprecation||LogicModule Replacement||Details||End of Support Date|
|In the existing version of this module, the wildvalue would get set to the same value for every instance, making all instances duplicates in most cases. Due to this all data was duplicated from a single instance. Wildvalues have been modified to ensure that they are unique. Additionally license types that are subsets of other licenses will now be filtered out if the parent license is not owned. This will ensure that expiration dates that are being reported, are only for licenses types that can expire.|
The datapoint DaysRemaining has been changed to report on expireTime instead of endTime, e.g. reporting on when the license expires instead of the end of the grace period. Grace period days are now no longer directly tracked but DaysRemaining will report negative values during the grace period, with a value of -90 being the standard time frame in which grace period licenses expire. Additionally minor changes to date processing have been implemented so additional date formats for license expirations can be parsed.
|September 15, 2023|
Azure Site Recovery Account
|N/A||The Azure Site Recovery Account and Azure Site Recovery EventSources cause alerts on the same events resulting in duplicate alerts. The Azure Site Recovery Account EventSource has been removed to avoid duplicate alerts.||September 15, 2023|
|Deprecated addCategory_MySQL and replaced it with the properly labeled addCategory_OracleMySQL. The new addCategory will put the version numbers on the resource if a successful connection can be made.||September 15, 2023|
In this section, you will find announcements about upcoming beta features, updates about ongoing beta features, and information about the end-of-support for existing features.
Migration of LogicModules from Settings 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.
Disclaimer: This feature is currently in Beta. Enterprise customers that are currently active in the New UI Beta are eligible to participate.
You can now view additional correlated metrics that are related to a numeric metric in alert. The new Datapoint Analysis feature will pull in relevant datapoints that are highly correlated to the alerting datapoint, and generates a correlation score. This correlation score is calculated based on datapoints retrieved by several different strategies like datapoints from the same instance. The higher the correlation score for a particular datapoint, the more correlated that datapoint is to the datapoint associated with the alert.
Cisco Catalyst SD-WAN
In a future release, you will be able to leverage the device-based modules that support Cisco SD-WAN Bulk API versions 20.6.x to 20.12.x (current release). LogicMonitor will provide a new Enhanced Script NetScan to automate discovering and onboarding each vEdge, cEdge, vSmart, and vBond device and to organize the Resources in Groups by SD-WAN Site ID. These modules will provide new features, an intuitive user experience, simplified ServiceNow CMDB Integration, and support for core LM Envision features like Network Traffic Analysis, Log Analysis, and Role Based Access Control.
Sunset of VNC and Telnet Remote Session Option
In a future release, we will deprecate VNC and Telnet to provide more secure alternatives for remote access; such as SSH, RDP, and HTTP(s). When this change is implemented, new portals will not see VNC and Telnet options in the user interface and existing users will continue to see these options until April 2024. Contact your Customer Success Manager if you need help migrating to other remote session types.
Sunset of API v1 and API v2
In a future release, we will sunset the LogicMonitor REST API v1 and API v2. However, support for API v1 and v2 will continue until October 2024. For more information, see LogicMonitor REST API v1 and v2 Sunset in the product documentation.
Recommendation: Migrate to LogicMonitor API v3. If you need help planning your migration, contact your Customer Success Manager.