LogicMonitor v.174 is scheduled to roll out to customer portals from August 17 through August 29.
Updated on August 29, 2022
- Fixed an issue that prevented a graph from being expanded properly on the Alerts page.
- Feature Highlights: New Microsoft Teams integration. Support for using the instance wildvalue as a unique identifier.
- General Updates: Added a new Settings page for OpenTelemetry Collectors, new aggregation functions to the logs query language, RBAC settings for Push Metrics LogicModules, and more.
- Updated Monitoring: New modules to monitor Azure backup and recovery, Kubernetes KSM nodes and pods, and AWS Cognito metrics and AWS Transfers.
New Microsoft Teams Integration
You can now integrate with Microsoft Teams to monitor your environment from within your Microsoft Teams. The Microsoft Teams Integration allows bi-directional communication between LogicMonitor and your Microsoft Teams channels to monitor alerts in LogicMonitor, send them to your Microsoft Teams channels, and then acknowledge and schedule downtime (SDT) from within a Microsoft Teams channel. This allows you to have a seamless experience between your LogicMonitor portal and your Microsoft Teams environment. For more information, see Microsoft Team Integration Overview in the product documentation.
Use Instance Wildvalues as Unique Identifier
For multi-instance datasources using scripted Active Discovery and either script or batchscript data collection, you can now use the wildvalue of the instance as the unique identifier. This feature allows you to rename the instance without losing its data history.
For example, the wildalias of an instance is
test1 and its wildvalue is
- If you select Use Wildvalue as Unique identifier and then rename the wildalias as
test2, LogicMonitor does not treat
test2as a new instance and continues to maintain its instance history.
- If you do not select this option, LogicMonitor considers
test2as a new instance, and the instance history of
test1will be lost if auto-delete is selected in Active Discovery settings.
For more information, see Use Wildvalue as Unique Identifier in the product documentation.
- Fixed an issue with alert evaluation for datasources.
- You can now manage OpenTelemetry Collectors from the Settings page. The OpenTelemetry Collectors tab is no longer accessible from the Exchange page.
- You now have the ability to scope role-based access controls for Push Metrics LogicModules (PushModules). Roles with only PushModule access cannot view or manage other available LogicModules (such as DataSources, EventSources, AppliesTo functions, and so on).
- Fixed an issue in the OpenMetrics wizard that prevented the details panel from scrolling properly.
- Fixed an issue that prevented users from saving OpenMetrics datasources with a large number of datapoints.
- Acknowledging an alert from within Microsoft Teams fails to log to the Integration Logs in LogicMonitor.
- When an alert is acknowledged from within Microsoft Teams, the Notes field in LogicMonitor incorrectly displays the alert as acknowledged for a Slack Integration.
- LogicMonitor inadvertently displays the error “Sorry there was a problem encountered with your request” when acknowledging or scheduling downtime for an alert in Microsoft Teams.
- Added new aggregation functions (average, minimum, and maximum) to the log query language.
- Updating the log query in a pipeline causes the pipeline to stop generating alerts. For alerts to work, you must create a new log pipeline.
- Fixed an issue that prevented the Anomaly filter from displaying in the Alerts report summary.
- Fixed an issue with inconsistent column names between CSV and HTML reports.
- For application topology, you can now view resource-based alerts under the Alert tab for a selected Node or Edge. Previously, you could only see service-based alerts.
- Added a new tab in the Mappings page, Node Graphs, to display the Alerts Analysis Graphs for a specific Resource at a given time range. This tab does not display graphs for Services.
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 under General Updates.
|New monitoring for AWS Cognito.|
|New monitoring for AWS Transfer.|
|New monitoring for Kubernetes KSM nodes and pods with Watchdog module continuously collecting data.|
|New monitoring for Azure Backup.|
|New monitoring for Azure Recovery Services.|
|New monitoring for Azure Replication Disaster Recovery.|
|Expanded functionality to Azure cloud resources.|
|CommonConfigs now attempt to provide metrics for successfully closing sessions. CommonConfigs with EXEC collection now filter out devices that incorrectly attempt interactive logins in EXEC mode.|
|Fixed incorrect metric paths.|
|Fixed a bug in logic determining whether to use 64-bit counters. Added new error message to provide more guidance when testing script.|
|Auto-delete for instances has been turned on and set to delete instance data stored on the backend if the instance has not been discovered for 30 days.|
SNMP AD timeout lowered.
Data Loss Warning: Data loss of incoming CiscoQoS data will occur on import if previously running CiscoQoS- 3.1 up to 3.3. We recently added discovery of incoming data in 3.1 on June 8th 2022 but found it was creating performance issues on some systems due to the increased load on collectors, if you need to continue to discover this data add a property to your resource named CiscoQoS.MonitorIncoming and set the value to true or that data will no longer be discovered. This setting will increase the load on your collector.
(Optional) Reduce Alert Noise and Remove class-default Instance: If you would like to reduce alert noise, number of monitored instances, and do not need to monitor class-default data you can add a property to your resource to stop discovering class-default data by adding CiscoQoS.IgnoreClassDefault and setting its value to true. This will cause data loss for class-default data where applied.
|Updated to account for certain API endpoints for blockCache being deprecated in later versions with no equivalent substitute existing at present.|
|Added alerts for kubeJobStatusFailed datapoint.|
|Updated alerts for Statefulset.|
|Added checks for CPU, memory, and network metrics.|
|Removed unnecessary toLong() conversions on inode datapoints.|
|Updated regex for output parsing to allow for outputs without spaces at the beginning of the line.|
|Updated display name to match style guidelines.|
|Added DataOffset datapoint to inform users of the difference in hours between the current time and the report time generated by Microsoft.|
|Added another pattern match for outputs showing MiB for memory and updated bytes graph to 1024 scaling.|
|Improved module descriptions.|
|Uptime may increase when imported because this module adds a method to find largest uptime value SNMP reports and collects that as the uptime. This module also adds collection the of engineBootCount counter to detect rollovers and consider their status in the cdp used to reduce false positive alerts from SNMP Engine on rollovers.|
Note: Updating the propertysource without updating the datasource can cause data alerts to not generate or can cause false alerts on SNMP devices that are running SNMP_Host_Uptime versions older that 1.4. Please update SNMP_Host_Uptime 1.4+ before updating the propertysource.
|Fixed a bug that prevented users from manually setting their own instance groups.|
|Provided a failover loop for localhost devices/collectors that are timing out due to the remote session inactivity.|
|Extended date regex to account for a new pattern and added debug mode for improved troubleshooting experience.|
|Refactored to reduce port checks, provide more meaningful error messages, and general code improvements.|
|Fixed an issue with KSM URLs.|
|Updated appliesTo to ensure Orchestrator-specific modules are not applying to appliance devices. Customers with duplicate monitoring on appliance devices should remove “SilverPeak_Orchestrator” from system.categories.|
|Updated ERT and added displayname ERI for Cisco server devices for CDP. Updated mapping to prevent setting interface MAC ERI for vPC HA Cisco devices, only CDP, due to incorrect mapping.|
|Improved handling with system category checks.|
|(1 SysOID Map)|
– \.1\.3\.6\.1\.4\.1\.5951\.1 (Netscaler)
|Added SNMP to assigned system.categories.|
|Improvements to matching Cisco switch bridge table entries to interfaces whose dot1dTpFdbPort does not match any interface index and to dot1dFdbPort interface mapping calculation. Mapping improvements; added equipment OUI to blocked keys, and reversed slot matching order.|
|Fixed OSPF erroneous SD-WAN endpoint edge.|
There are no deprecated modules in this release. For the history of deprecated modules, see Deprecated LogicModules.
In this section, you will find announcements about upcoming beta features, updates about ongoing beta features, and information about the end-of-life of existing features.
New UI Preview for Resources and Reports
We are in the process of rolling out a new user experience (UX) for the Resources and Reports pages in your LogicMonitor portal. The new UX is designed to streamline workflows, reduce clicks, and includes new features. Once released, you can enable the new UX using a toggle that is available on each of the pages. This New UI Preview toggle allows you to switch between the current and new versions of the user interface.
We will maintain this preview toggle while we monitor usage and gather your feedback. We will provide more information before we remove the toggle and transition completely to the new UX.
MGD Collector 31.004 Release
The next MGD Collector is scheduled for release on September 29.