v.146 Release

IMPORTANT: Beginning with the rollout of v.146, LogicMonitor is updating its new version deployment window to 7:30-10:30 p.m. PT (previously, the window was 6-9 p.m PT). We will continue to provide in-app notification 48 hours in advance of a new version deployment.

General Enhancements and Fixes

Alerting

• Ability to link alert to its associated components. The alert detail pane now provides hyperlinks to the resource/website/service associated with the alert and the DataSource (if applicable).
• (FIX) Alert acknowledgement. Resolved an issue that was causing exceptions when users with a particular combination of permissions attempted to acknowledge alerts.
• (FIX) Cleared ConfigSource alerts. Fixed issue preventing cleared alerts triggered by ConfigSources from displaying in the Alerts page.
• (FIX) Time zones in graph legends. Resolved issue where graph legends (as displayed on the Graphs tab of the alert detail pane) were not honoring the user’s configured time zone.
• (FIX) Severity icon display. Resolved an issue preventing the display of severity icons in some cases when viewing the pop-out version of an alert from the Alerts page.

Cloud Monitoring

• AWS updates:
  • AWS Bahrain region added. Added support for the AWS Bahrain region (me-south-1), which is the first AWS region in the Middle East. Customers can now monitor services in the Bahrain region that are supported by LogicMonitor’s AWS monitoring.
  • New StorageType property for AWS RDS. Added StorageType as a property for AWS Relational Database Service (RDS). This new property (system.aws.storageType) allows logical grouping and filtering according to StorageType.
  • (FIX) AWS Kinesis Streams permissions. Previously, AWS Kinesis Streams permissions were not being properly tested. In some cases, this resulted in customers not being alerted that additional permissions were required to be able to monitor AWS Kinesis Streams from the LogicMonitor portal. This issue has been resolved.

Dashboards

• Alert List widget. The behavior of the anomaly filter available in the alert list widget configurations now aligns with that of the anomaly filter available on the Alerts page.
• (FIX) Custom Graph widget. The Custom Graph widget was returning an “invalid virtual datapoint expression” error when attempting to calculate virtual datapoints that referenced datapoints belonging to the same DataSource, but applying to different resources. This issue has been resolved. If you previously experienced this issue, open the Custom Graph widget configuration dialog and simply save the current configurations – no edits are necessary.
• (FIX) Rounding of Y-axis values. In some cases, the Y-axis value for some graphs was not displaying as a rounded value. This issue has largely been resolved, although there is still a remaining corner case that we are actively working on where non-rounded values still display if display type is selected as “Line” and data is constant (data is displayed in a straight line) for virtual datapoints

Kubernetes Monitoring

The following new features and improvements will be available with the new v5.0.0 version of Argus, which is targeted for arrival in early January.

• Avoiding name conflicts in discovery. To avoid name conflicts and subsequent issues with discovery, the following enhancements were made:
  • Resource type (for example, “Pod”) is appended by default to the LogicMontior display name
  • New Argus Helm chart options, FullDisplayNameIncludeNamespace and FullDisplayNameIncludeClusterName, are available to append namespace and cluster name respectively to the LogicMonitor display name (default: false). You may find that enabling one of these two new options is useful for avoiding naming conflicts in cases where pods with the same names are running across multiple namespaces and/or clusters.
  • For resources that fail to be added due to name conflicts, the conflicting resource will be added to a dynamic group named “_conflicts”.
• Discovery filtering by pod name. Pod name is now available for use with discovery filtering, including handling of special characters such as hyphens. You may find this useful for filtering pods in/out of monitoring based on names rather than labels.
• Discovering EKS Fargate nodes and pods. Previously, nodes and pods for EKS Fargate weren’t being discovered properly due to shared IPs, but no host network specification in the pod manifests (EKS Fargate pods each run on a distinct node and share IPs, but don’t use the Kubernetes Host Network specification). To account for this, we’re now categorizing pods with the EKS Fargate label “eks.amazonaws.com/fargate-profile” as pods configured with host networking. This will ensure (1) the right value for the system.hostname property gets set, (2) the right DataSources apply, and, most importantly, (3) there are no discovery conflicts between pods and nodes for EKS Fargate.

LM Exchange

• New LogicModule statuses. LogicModule statuses “Beta” and “Deprecated” now display in the LogicModule metadata table.

LM Logs

• Log events +/- three hours no longer accepted. Log events with timestamps more than three hours in the past or future are no longer accepted, and will result in a new 4006 API response code. This is to ensure relevance of data and protect against misconfigured timestamp settings.

Network Traffic Flow Monitoring

• New benchmarks. New capacity benchmarks for network traffic flow have been published for the Large, XL, and XXL Collectors. These benchmarks show a dramatic increase in the number of flows per second that can be comfortably monitored and were reached as a result of an ongoing initiative to enhance and optimize LogicMonitor’s network traffic flow monitoring capabilities. See Collector Capacity for the new benchmarks.
• Support for sFlow version 5. Added support for sFlow version 5 (Collector version 29.105 or higher is required).
• DNS lookups. Increased the DNS cache storage duration to 24 hours (previously duration was 30 minutes) to resolve repeated DNS queries preventing the resolved names from displaying.
• (FIX) IPv6 address format display. Normalized IPv6 address format display for NetFlow IPv6 endpoints that do not resolve via DNS.

REST API

• (FIX) Locked API tokens. Previously, locked API tokens due to multiple unsuccessful authentication attempts were causing an exception to occur. This issue has been resolved.
• (FIX) Updating a device via PATCH request. Previously, submitting a PATCH request to modify both a device “name” and its customProperties would result in the device name updating to the name of one of the customProperties. This issue has been resolved.
• (FIX) /apiStats/externalApis. Previously, /apiStats/externalApis was returning separate values for API calls to the same endpoint depending on whether the user made the call with or without a trailing forward slash (/). This has been corrected and calls with either variation are now appropriately identified and aggregated as a single entry in the response.

Website Monitoring

• New Web Check properties. Several new properties are now available for manipulating the settings of Web Checks. Specifically, these settings provide some flexibility in cases where sites may load slower than the default timeouts used by LogicMonitor’s external checkpoints.

  The following built-in properties all default to 30 seconds and all support an acceptable value range between >0 and <=60.

  • website.http.client.so.timeoutInSec (socket timeout in seconds)
  • website.http.client.connect.timeoutInSec (TCP connection timeout in seconds)
  • website.http.client.read.timeoutInSec (read timeout in seconds)

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.

Beta for Push Metrics API is targeted for January. If you have a compelling use case and the resource availability, and would like to be considered for participation, please complete the Customer Beta survey.