v.145 Release

General Enhancements and Fixes

Alerting

• Bulk alert acknowledgement. The new UIv4.1 version of the Alerts page, rolled out in v.143, now supports the ability to acknowledge multiple alerts at once.
• Dynamic threshold usage limit. The usage limit calculation for dynamic thresholds has been updated to use the contracted resourced count rather than the current resource count. The new calculation (contracted resource count * 8) more accurately (and consistently) reflects dynamic threshold usage limits.
• (FIX) Alert overview graphs. Customers without access to the dynamic thresholds feature were receiving permissions errors when attempting to view the overview graph that displays as part of the Overview tab of an alert’s detail view (found on the Alerts page). To resolve this issue, overview graphs will no longer attempt to load expected ranges in portals where dynamic thresholds are not supported.
• (FIX) Detail URL for cleared alerts. When opening the detail views for cleared alerts in new browser tabs—either from the LogicMonitor interface or from delivered alert notifications that incorporate the ##ALERTDETAILURL## token—the resulting web pages were opening as blank pages. This has been fixed.

Cloud Monitoring

• AWS updates:
  • AWS Africa region added. Added support for the AWS Africa region (af-south-1), which is the first AWS region in Africa. Customers can now monitor services in the AWS Africa region that are supported by LogicMonitor’s AWS monitoring.
  • Updated AWS Direct Connect connection state mapping. AWS Direct Connect is changing from a “default to unavailable” to a “default to available” for monitoring. There remain two connection states for removing instances (“Deleting” and “Deleted”) and three connection states that are unavailable for monitoring (“Requesting”, “Ordering” and “Rejected”). Remaining connection states will map to an available state, allowing clients to monitor in LogicMonitor.
  • Using recommended AWS STS methods. LogicMonitor has updated the method it uses to obtain cross-account authorization tokens from AWS Security Token Service (STS). The new method follows AWS’ best practices and will allow for easier future addition of new AWS regions to the LogicMonitor portal. No action is required on the customer’s end.
  • (FIX) AWS Trusted Advisor API. As a result of changes made to the AWS Trusted Advisor API, several DataSources were not associating: AWS_IAM_ServiceLimits, AWS_VPC_TrustedAdvisorServiceLimit, and AWS_EC2_TrustedAdvisorServiceLimits. To resolve this issue, LogicMonitor has updated the method for validating and calling the Trusted Advisor API.
• Azure updates:
  • Name adjustments for Notification Hubs and SQL Elastic Pools services. Previously, when attempting to change the display names of Notification Hubs and SQL Elastic Pools services with forward slashes (/) in their resource names, errors were returned. To resolve this issue, forward slashes found in the names of Notification Hubs and SQL Elastic Pools services will be replaced with colons (:). Note: Only resource names are affected by these changes; forward slashes may still appear in display names, where permitted.
  • (FIX) Billing data calculations. There was an issue in calling cached RateCards to calculate the Azure billing data. This is fixed and should require no action from the clients.

Collectors

• EA 29.104. Collector version EA 29.104 was released on November 10. Collector releases are deployed independently of LogicMonitor platform releases. For more information on the various Collector versions available for upgrade and the differences between EA (early access), GD (general deployment), and MGD (minimum general deployment) versions, see Collector Versions.

Dashboards

• (FIX) NOC widget. Instance-level filters containing OR operations, as formatted with the pipe symbol (|), were not being correctly evaluated, causing a “Resource Not Found” error to be returned by the widget display. This has been fixed.

LM Exchange

• (FIX) LM Locator code display. The LM Locator code was not displaying for installed LogicModules. Impacting the Exchange and Settings pages, this has been fixed.

Network Traffic Flow Monitoring

• (FIX) NBAR2 application type. Application type (as sourced from NBAR2) was not displaying properly in the Traffic Tab visualizations for network traffic flow data. This has been fixed.

Role-Based Access Control

• Improved error handling when acknowledge privileges are missing. More descriptive error messages are now returned when users with SDT-only or threshold-only privileges for a resource attempt to acknowledge alerts triggered by that resource.

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.