v.149 Release

v.149 of the LogicMonitor portal is scheduled to roll out to customers from March 8 through March 17.

General Enhancements and Fixes

Alerting

• (FIX) Addressed several issues related to initiating SDT from the Alerts page:
  • Fixed issue preventing SDT in durations of weeks, months, or years from being scheduled.
  • Fixed issue preventing the SDT icon from being immediately shown after setting SDT for an alert.
  • Fixed issue preventing SDT initiation for the device associated with an alert.
  • Attempting to initiate SDT from the old Alerts page UI (available by transforming “/alerts” to “/alert” in the URL) was causing a blank page to be generated. This has been fixed and SDT can now be initiated from the previous UI version of the Alerts page.

• (FIX) Improved warning message when acknowledging a previously acknowledged alert. When acknowledging an alert that was previously acknowledged, LogicMonitor now displays a descriptive warning message:  “Alert <ID> has already been acknowledged”. Previously, the warning consisted of a 400 error.

Audit Logs

• (FIX) Unnecessarily capturing unchanged static thresholds. Previously, LogicMonitor’s Audit Logs were unnecessarily capturing unchanged static threshold data when dynamic threshold data was updated at the resource group level. This has been fixed and Audit Logs now only capture details of dynamic threshold updates.

Cloud Monitoring

• (FIX) Microsoft Azure. The Azure File Storage Capacity was not triggering an alert because the allowed delay time limit was too short. This delay time has been increased (default 2 hours). Added GCC configurations: azure.collector.allowedDelay and azure.allowedDelay.collectionTypes.
• (FIX) Microsoft Azure. Added subscriptionId as additional argument to string.format() to fix an issue where Azure Advisor EventSource was not working.

Collectors

• EA 29.106. Collector version EA 29.106 was released on February 10. This version fixes the known issue present in versions 29.101 through 29.105 that caused resources with heartbeats to be incorrectly marked as dead/down.

Collector releases are deployed independently of LogicMonitor platform releases. For more information on the different Collector versions available for upgrade, see Collector Versions.

LM Logs

• (NEW) Added RBAC support! New Logs permissions for: viewing logs, viewing pipelines, and managing pipelines are now available within roles. You may find this useful for controlling which users can see which logs, and who can create alert conditions. To view logs, a user also needs access to the resources the logs are associated with.

Note: Users who don’t have access to all resources will only be able to view logs for up to 300 resources when no filters are used on the Logs page. This will be fixed in an upcoming release. To avoid this, use at least one filter as a workaround.

• (HOTFIX) Some customers were unable to Add Role when LM Logs was disabled. A fix for this has been deployed.
• (NEW) Multiple resource selection in Pipelines. You’re now able to select more than one resource when creating pipelines.
• (NEW) Two new resource group filtering options were added to the Logs page, allowing you to (1) filter logs associated with resources directly in the selected group and (2) filter logs associated with resources in the selected group AND its subgroups. These filters may be useful for displaying desired logs more efficiently.
• (ENHANCEMENT) Log Alerts. Consistent with other alert types, users can now un-acknowledge log alerts.
• (ENHANCEMENT) Log Alerts. Removed the option to create log alerts from a row in the logs table if at least one log processing pipeline does not exist, because alert conditions are created within pipelines.

Dashboards

• (FIX) NetFlow widget. Previously, the NetFlow widget only displayed the top 10 flows, regardless of the number specified (10, 20, 50 or 100) when configuring the widget. This has been fixed.
• (FIX) Top Applications pie chart not properly rendering on dashboard. Previously, when the Top Applications pie chart was added as a widget to a dashboard (from the Traffic tab), the pie chart remained static, only displayed a solid circle at 100%. This issue has been fixed and the pie chart now correctly displays percentage segmentations when viewed from a dashboard.

Kubernetes

• (FIX) Argus v5 was crashing in some cases following API rate limiting. This has been fixed.
• (ENHANCEMENT) Added Kubernetes Monitoring support for Kubernetes 1.20.

Netflow Traffic Monitoring

• (ENHANCEMENT) Improved support for Cisco ASA devices. Previously, some Cisco ASA devices were not showing network traffic flow data. To resolve this issue, LogicMonitor now accepts alternative initiator and responder fields from the ASA flows to fulfill field requirements.

Important: Collector version 29.107 or higher is required for this enhancement; 29.107 has not yet been released.

Resources

• (NEW) New system.hoststatus property. A new auto-assigned system information property named system.hoststatus has been added for all on-premises devices (it is not applicable to cloud resources). This property updates the status of the device every two minutes. Valid values for this property are:
  • normal – device and associated Collector host are both up
  • dead-collector – device’s associated Collector host is down device and Collector host are both down
  • dead – device is down and associated Collector host is up

Reporting

• (FIX) Alerts report. Log alerts weren’t being reflected in the output of the Alerts report. This has been fixed.
• (FIX) Email notification of report generation failure. When LogicMonitor determines that a report will take a long time to generate, the user is notified that results will be delivered via email. However, if the report were to subsequently encounter an error, users were not being notified via email that generation had failed. This has been fixed. 
• (FIX) Resource Metric Trends report. Two updates have been made to the Resource Metric Trends report:
  • Duplicate graph lines. Previously, this report created duplicate graph lines if duplicate datapoints were present. To resolve this issue, instance checks are now performed while generating graphs and identified duplicate datapoints are treated as a single datapoint with a single plotting.
  • Differing timestamp formats. Previously, the timestamps that displayed when hovering over a point on the graph featured differing formats depending on the duration of the reporting period. This has been fixed and all timestamps are now uniformly formatted.

REST API

• (ENHANCEMENT) More precise error messages for appliesTo field updates. Previously, if a request to update the appliesTo field was made by a read-only user and an incorrect value for the logicModuleId field was provided, the response generated was “Unknown error.” This has been fixed and responses now precisely detail the reason for the error.
• (ENHANCEMENT) More precise error messages for “Invalid json body” errors. The general error response message of “Invalid json body” has been enhanced to additionally include information about the cause of the exception.
• (FIX) Incorrect value returned for the enableFailOverOnCollectorDevice field when Collector is a member of an ABCG. Previously, the API response provided by a request to the  /setting/collector/collectors/{id} endpoint would return the incorrect value of “false” for the enableFailOverOnCollectorDevice field when the Collector was part of an ABCG (Auto-Balanced Collector Group). This has been fixed and the value of “true” is now returned in this case.

User Interface

• (FIX) Pagination preservation. Previously, pagination on the Alerts page was sticky. This has been fixed and pagination is now appropriately reset once you navigate away from the Alerts page.
• (ENHANCEMENT) Topology Mapping. Updated map icons and hover behavior to be consistent with new UI.

User Management

• (FIX) Permissions for Big Number widget on dashboards. Big Number widget (including resourceCount metrics) should be visible for users with Manage permissions on Dashboard and View permissions on the Resources.

New, Updated, and Deprecated LogicModules

New LogicModules

Updated LogicModules

Deprecated LogicModules

LogicMonitor deprecates LogicModules when we have published a replacement LogicModule that provides superior access to the monitored technology (for example, supports more versions of the technology or provides improved scalability).

However, there may be times when a LogicModule is deprecated with no replacement (for example, when a technology becomes defunct or security issues beyond LogicMonitor’s control arise).

Note: When importing a replacement LogicModule, you will not experience any immediate data loss due to the name variation that LogicMonitor expressly adds. However, there will be a diversion in data collection between the deprecated and new LogicModule, and you will potentially collect duplicate data and receive duplicate alerts for as long as both LogicModules are active. For this reason, we recommend that you disable monitoring of the DataSource instances at the resource or resource group level after you have imported its replacement. When DataSource monitoring is disabled in this way, it stops querying the host and generating alerts, but maintains all historical data. At some point in time, you may want to delete the legacy DataSource altogether, but consider this move carefully as all historical data will be lost upon deletion. For more information on disabling DataSource monitoring, see Disabling Monitoring for a DataSource or Instance.

Entering Beta

Alert Grouping with New Header Graph on Alerts Page

Recently released as a beta feature in v.148 for all Enterprise and Enterprise MSP customer accounts, the Alerts page incorporates a brand new time-series header graph that provides immediate visual insight into an alert storm or other event requiring investigation.

Beta for this new header graph will continue in v.149 as we make performance improvements and align the graph filters with the Alerts page filters.

For more information on using this new alert header graph, see Managing Alerts from the Alerts Page.

Push Metrics API

LogicMonitor is developing a Push Metric API in order to allow metrics to be sent directly to LogicMonitor without the use of a Collector. 

The first phase of the beta, which consists of a REST API that features endpoints for metric ingestion, has been ongoing since early January. The second phase of the beta, which we opened up in early February and includes the addition of a Python SDK, is continuing as well.

If you are interested in participating in the first phase and would like to expand your testing to include the new Python SDK, see the Push Metrics API Solution guide. If you are not currently participating in the first phase, please complete the Customer Beta survey and use the comments section to indicate your interest in participating in testing for the Push Metrics API Python SDK.

Looking ahead: Sunset of RPC API

We have decided to focus on improving the LogicMonitor REST API, which has higher security standards and integration capabilities more in-line with our future development goals. This means that we are preparing to end support for the RPC API after this summer. If you are using the RPC API for Ansible, reach out to Support for guidance on migrating playbooks to the REST API.