v.147 Release

General Enhancements and Fixes

Alerting

• New “Suppression Type” alert filter. A new alert filter (and alert table column) provides visibility into alerts whose notifications are suppressed by LogicMonitor for the purpose of reducing unnecessary alert noise. The new filter allows you to organize alerts according to the reason behind notification suppression. There are five available suppression types that can be used as filter criteria:
  • None. Returns alerts whose notifications have not been suppressed. (Note: Refrain from using the None filter criterion as it is not working as intended. This is a known issue that will be addressed in an upcoming release.)
  • SDT. Returns alerts whose notifications have been suppressed due to scheduled downtime (SDT) of the triggering resource/instance.
  • Host Down. Returns alerts whose notifications have been suppressed because the Collector has not been able to access the triggering resource (host) for a period of six minutes or more.
  • Cluster Alert. Returns alerts whose notifications have been suppressed because the triggering resources/datapoints are members of a cluster alert and the cluster alert has been configured to supersede the individual alerts.
  • Collector Down. Returns alerts whose notifications were suppressed as a result of being triggered by devices impacted by a down Collector.
  • Anomaly Detection. Returns alerts whose notifications were suppressed as a result of being determined non-anomalous by LogicMonitor’s dynamic thresholds.

  Note: To include the accompanying suppression column in your alert table, you’ll need to customize the column settings for your alert table. To learn more about filtering alerts and customizing alert table settings on the Alerts page, see Managing Alerts from the Alerts Page.

• (FIX) Alert notification sound not playing. In the prior version of the Alerts page, which is accessible by removing the “s” from the very end of the Alerts page URL (transforming “/alerts” to “/alert”), alert sounds were not playing upon arrival of alerts. This issue has been fixed.
• (FIX) Error on opening anomaly detection version of graph from Alerts page. Previously, when attempting to open the anomaly detection version of a graph from the Graphs tab that displays in an alert detail summary, an error was returned. This has been fixed.
• (FIX) Alert clear notifications not delivered during SDT. Previously, LogicMonitor would only deliver alert clear notifications during scheduled downtime (SDT) if alert creation time occurred before SDT start time. Now, alert clear notifications will be delivered during SDT regardless of alert creation time.
• (FIX) Alerts erroneously referencing dynamic threshold as trigger. Previously, alerts generated by static datapoint thresholds with a Delta operator were referencing dynamic thresholds as trigger if dynamic thresholds were also configured for the datapoint. This issue has been fixed.

Audit Logs

• Capturing dynamic threshold updates at resource group/instance levels. LogicMonitor’s Audit Logs now comprehensively capture updates made to dynamic thresholds at the resource group/instance level (from the Resources page).

Cloud Monitoring

• AWS updates:
  • Discovery improvements for AWS SQS. Previously, AWS did not support pagination and only returned the first 1000 Simple Queue Service (SQS) resources. An update from AWS now allows LogicMonitor to discover SQS resources beyond the initial 1000 SQS resources. Note: If you have more than 1000 SQS resources, this discovery improvement could result in an increase in the number of billable cloud resources.
  • New system properties for monitoring AWS RDS. LogicMonitor now sets four new system properties for AWS Relational Database Service (RDS) resources for the purpose of limiting data collection to RDS instances with Performance Insights enabled. These properties are:
    • system.aws.performanceInsightsEnabled
    • system.aws.performanceInsightsKMSKeyId
    • system.aws.performanceInsightsRetentionPeriod
    • system.aws.dbiResourceId

Kubernetes Monitoring

• New Argus version available. The new v5.0.0 version of Argus is now available. As with all major Argus version releases, opt-in is required. See Upgrading Kubernetes Monitoring Applications for upgrade details and enhancements featured in this new version.

LM Logs

• (FIX) Intermittent log visibility on Logs page. Fixed an issue that was preventing the display of new logs on the Logs page, even upon page refresh.
• (FIX) ELB logs incorrectly mapped to LM resources. Fixed an issue that was preventing correct mapping of ELB logs forwarded from sub-directories in an S3 bucket.

Network Traffic Flow Monitoring

• NetFlow Health widget. The Traffic tab now displays an expandable/collapsible widget that provides network traffic flow monitoring health at a glance. This widget highlights the status of several key network flow markers and graphs the last 60 minutes of network traffic monitoring activity.

  Because there is not always an obvious sign that network traffic flow monitoring has been diminished or interrupted, this new widget will serve to provide an earlier warning for time sync issues or high volumes of malformed templates or flows.

  

  Note: This widget requires Collector version 30.100 or greater. Because this version is not yet available, the widget will be auto-collapsed upon release.

Reporting

• (FIX) Dynamic threshold settings not reported. Previously, dynamic thresholds configured for datapoints were not displaying in the output of the Alerts Thresholds report (or on the Alert Tuning tab). This issue has been fixed.
• (FIX) Resource Metric Trends report. In some cases, the Resource Metric Trends report was including negative values on its y-axis scale—even when all reported datapoint values were positive. This issue has been fixed.
• (FIX) NetFlow Device Metric report. IPv6 resolved DNS hostnames now display in the NetFlow Device Metric report.

Topology Mapping

• (FIX) Higher-priority ERTs not assigned. Previously, a higher-priority External Resource Type (ERT) would not be set on a device if a lower, different category ERT was present. This issue has been fixed.

User Interface

• (FIX) Erroneous display of dynamic threshold usage warning upon login. Previously, LogicMonitor erroneously displayed a warning message upon portal login that the allowed limit for configured dynamic thresholds had been exceeded. This issue has been fixed.
• (FIX) Missing note prompt when updating static datapoint thresholds at resource group/instance level. Upon removing, adding, or updating static datapoint thresholds at the resource group or instance level (from the Resources page), users were no longer being allowed to add notes to accompany the action for display in the static threshold history. This ability had been inadvertently removed in a previous version, but has now been returned.

New, Updated, and Deprecated LogicModules

Recently released to the LogicMonitor public repository, our new and updated LogicModules are available for import to expand and enhance your monitoring coverage.

New LogicModules

Updated LogicModules

Deprecated LogicModules

LogicMonitor deprecates LogicModules for a variety of reasons. Most often, it is because 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 are 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

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. Some technology landscapes where this capability is becoming vital include server-less infrastructures such as AWS Lambda, large distributed microservices environments with custom metrics (including business metrics), and IoT environments.

The first phase of beta for Push Metrics API is underway! In this first beta phase, a REST API is provided for beta participants that features endpoints for metric ingestion, resource property update, and instance property update.

In the second beta phase (targeted for the later half of Q1 2021), the REST API and a Python SDK will additionally be available for beta participants. We plan on making other language-specific SDKs available soon after.

If you have a compelling use case and the resource availability, and would like to be considered for participation in either the first or second beta phase, please complete the Customer Beta survey. In the comments section please let us know if you would like to use the REST API directly, via Python SDK, or have a request of another language-specific SDK such as Go, Java, or .NET.

Cloud Integrations in LM Exchange

In this beta release, we’ve made some cloud integrations available through LM Exchange in your LogicMonitor portal. LM Exchange will make it possible for you to sort and filter for modules by type or status, for example, to see when upgrades are available or to review all the LogicModules available in a package.

Specifically, for this beta, the AWS cloud integration onboarding has received a facelift and can now be initiated from LM Exchange. Microsoft Azure and GCP will follow suit in future releases.

Also, as part of this beta, we are beginning our SaaS API authentication for Office365—with more SaaS solutions (Zoom, SalesForce, and so on) to follow in coming releases. This marks a new method for agentless collection of SaaS application metrics.

If you are interested in participating in the beta program for SaaS integrations, reach out to your LogicMonitor representative. Ideal partners are already leveraging cloud monitoring and are willing and able to integrate with at least one Office 365 subscription and participate in feedback rounds.