LogicMonitor v.182 is scheduled to roll out to customer portals from February 15, 2023 through February 27, 2023.
- Feature Highlights: Released Logs query tracking. Open beta releases of SaaS integrations for Webex and Slack, and new UI for Resources, Reports, and Services pages.
- General Updates: Improvements to Logs CSV downloads and added support for updating the linked user in the Microsoft Teams integration.
- Updated Monitoring: New modules to monitor Kubernetes roles, role bindings, and cluster role binding; Microsoft SQL Server usage; and Webex services.
Logs Query Tracking Release
Logs Query Tracking is now available to all Logs users. Query tracking allows you to generate metrics from log data. When you mark a saved search for tracking, the query runs every 5 minutes and stores the number of logs and number of anomalies as instance data. Having this information as metrics allows you to view trends over time in LogicMonitor Dashboards and create alerts with static and dynamic thresholds when log counts fall outside an expected range. For more information, see Logs Query Tracking in the product documentation.
SaaS Integrations for WebEx and Slack Open Beta Release
New SaaS integrations, Webex and Slack, are now available as an open beta to all users. These new integrations can provide a better understanding of the availability, usage, and performance of your Webex and Slack instances. These integrations will be available with no additional cost during this open beta period; after this feature is officially released, existing SaaS charges will apply. We encourage you to set up these integrations and provide us with feedback. For more information, see Webex Monitoring and Slack Monitoring in the product documentation.
New UI for Resources, Reports, and Services Open Beta Release
Note: This open beta is currently limited to participating users. In the coming weeks, this open beta will be made available for all users.
We’ve reworked parts of the LogicMonitor user interface (UI) to enhance your experience of the platform. With LogicMonitor v.182, you will have access to the new UI for Resources, Reports, and Services via a toggle at the top of the page that lets you navigate between the current and new UI. We encourage you to take a look and provide us with feedback so that we can continue to improve the experience for you. For more information, see LogicMonitor New UI Documentation in the product documentation.
- Fixed an issue where Root Cause Analysis suppressed the wrong alerts.
- Fixed an issue where disabled Alert Thresholds were not showing as disabled.
- Fixed an issue where Azure Monitor metrics were not collected properly for some resource types.
- You can now update the linked user in Microsoft Teams that is used for Acknowledging alerts and putting alerts into Scheduled Downtime (SDT). We recommend that you create a generic Microsoft Teams integration user for this integration before you update the linked user in the Microsoft Teams Channel by clicking the button “Update Linked User”.
- Logs CSV download now includes all viewable columns in the Logs table. Toggle columns on and off via the fields panel.
- You can no longer access the Legacy Exchange page from the main navigation. The Legacy Exchange page included Cloud Integrations, Synthetics, OpenTelemetry Collector, and Open Metrics datasources.
- You can create and edit Cloud integrations and Synthetics checks from the Resources page.
- You can create and edit Open Metrics datasources from the Modules > My Module Toolbox page.
- You can create and edit OpenTelemetry Collectors from the Settings page.
- Fixed an issue where SNMP SysOID Maps would not load in the diff view during update attempts.
- Fixed an issue where Alert Thresholds Reports did not display disabled alerts correctly.
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 under General Updates.
|New modules to monitor usage of database and transaction log space. For more information, see Microsoft SQL Server Monitoring in the product documentation.|
|New Webex SaaS integration modules to monitor meeting quality of service, report general user stats for all users in the organization, and report the license usage of different Webex services.|
|New modules to monitor Kubernetes roles, role bindings, and cluster role binding.|
|Refactored Kubernetes ConfigSource to improve error handling.|
|Updated appliesTo conditions to ensure that irrelevant modules were not applied to Kubernetes resources.|
|Increased the collection interval, and corrected metric paths.|
|Updated datapoints including adding DatabaseMemoryUsagePercentage and EngineCPUUtilization, and removing extra unused datapoints recently introduced.|
|Added EndpointHealthyENICount and EndpointUnHealthyENICount datapoints. |
Created EndpointHealthyENICountNormalized and EndpointUnHealthyENICountNormalized.
Graphed Normalized datapoints in ENI Count graph.
|Updated modules to remove leading and trailing whitespaces from inputs and include new general debug messages showing configured properties.|
|Removed Open Telemetry Collectors from this module because the data provided is not accurate for this type of collector.|
|Added support for user-defined API URL via host property mist.api.url to expand support to additional regions. Changed “No Data” to “0” when no alarm data is detected. For more information, see Juniper Mist Monitoring in the product documentation.|
|Sets all invalid status codes to 4. Valid status codes are 1, 2, 3, and 4.|
|Fixed an issue with regex pattern matching.|
|Updated the duration in the graph for the Microsoft_Azure_BackupJobStatus DataSource to show the metric in minutes.|
|Added new metric: IndexCapacity.|
|Updated Active Discovery schedule and instance persistence.|
|Update description of protectionState.|
|Added lookup table for state code.|
|Set the default WMI call timeout to 30 seconds. Added the property “windowscpu.wmi.timeout” to give the option to increase the timeout.|
|Removed alerts, and filtered out newlines in the error message for instance level properties.|
This module informs users of configuration issues. Other modules in this package provide monitoring information and alerts. For example, Oracle_Database_ConnectionStatus alerts users of connection issues.
|Improved error handling following security best practices.|
|Fixed an issue in the comparison of record numbers that prevented accurate data collection. Updated appliesTo statement to automatically apply devices using: “isWindows() && lmlogs.winevent.channels && lmaccess.id && lmaccess.key”.|
|Fixed an issue when calculating the start time for API query window that caused the look back window to be hours instead of minutes.|
|Added a new host property cohesity.alertignore that allows user to choose alert names to be suppressed and fixed a bug in lookback polling interval.|
|Updated appliesTo criteria to include AWS and Azure cloud virtual machines.|
|Fixed an issue in the variable type declaration.|
|Updated blockedKeys and fixed ERT detection to use Linux keywords.|
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.
Deprecation and Replacement
|Details||End of Support Date|
|Renamed the datasource and updated metric paths to follow AWS changes, and updated datapoints and graphs.||2023-02-21|
|Renamed the datasource and updated the datapoint description.||2023-02-16|
|Replaced mentions of Elasticsearch with OpenSearch and fixed linting issues.|
Note: Historical data will be lost after migrating to this new module.