General Enhancements and Fixes
- 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.
- 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.
- 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.
- (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.
- (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.
|(DataSource) A new scripted DataSource for monitoring Cisco CPU usage has been released that uses an additional OID to resolve duplicate wildvalues. In addition, a new datapoint has been added for five-minute CPU usage.
Note: This new DataSource deprecates CiscoCPU-. Due to merging of wildvalues, historical data for the now-deprecated DataSource may not be accurate. See the Deprecated LogicModules section of these release notes for details on how to transition from a deprecated to a replacement LogicModule.
|(2 DataSources) Monitors WAN uplink status, latency and packet loss.
|(DataSource) Gathers metrics for transformations and inspections as well as counts of findings, job results, and trigger runs.
|(DataSource) Tracks responses returned by type from the GCP CloudDNS resolver.
|(DataSource) Monitors CPU, memory and network metrics for GCP Cloud TPUs (Tensor Processing Units).
|(DataSource) Monitors autoscaler utilization and serving capacity.
|(2 DataSources) These DataSources replace the now-deprecated Liebert Power lines, Liebert Temperature probes-, and Liebert UPS Temperature probes- DataSources. See the Deprecated LogicModules section of these release notes for details on how to transition from a deprecated to a replacement LogicModule.
Updates: Rewrote as scripted SNMP; merged monitoring of temperature and UPS temperature probes into a single DataSource; added new power and voltage metrics for power lines monitoring; fixed an incorrect filter for power lines.
|(5 DataSources, 1 PropertySource) Complementing the existing LogicMonitor_Portal_APIUtilization DataSource, the LogicMonitor Portal monitoring package, which leverages the LogicMonitor API to monitor the status of your LogicMonitor portal, now features a total of seven LogicModules. For setup and monitoring details, see LogicMonitor Portal Monitoring.
Note: The existing LogicMonitor_Portal_APIUtilization DataSource has been updated as part of this release.
Note: The LogicMonitor_Portal_Metrics DataSource is deprecated by the release of these new modules. See the Deprecated LogicModules section of these release notes for details on how to transition from a deprecated to a replacement LogicModule.
|Monitors CoreDNS caching and DNS request activity metrics.
|Microsoft Azure ExpressRoute Virtual Network Gateways
|(DataSource) Created new DataSource to separate monitoring functionality of the ExpressRoute virtual network gateway type from the existing Microsoft_Azure_VirtualNetworkGateway DataSource.
|(PropertySource) Narrowed the AppliesTo logic to require the presence of the tintri.user and tintri.pass properties on the device to prevent unnecessary API calls and reduce Collector load.
|(DataSource) Updated collection and Active Discovery script to accommodate the return of null values for metrics and properties.
|(9 DataSources) Updated technical notes to state that the collections script requires the DataSource name to remain unchanged.
(PropertySource) Refactored the collection script to use the Groovy HTTP library instead of the Collector’s HTTP library to address discovery failures; added missing parameter to function call that was causing script failures.
|(DataSource) Converted script to Groovy due to authentication issues with PowerShell. This DataSource now uses the same authentication scheme as the other LogicModules in the Citrix XenApp monitoring package.
|JIRA Issues Count
|(DataSource) Updated the collection script to use an updated API authentication method; the method previously used by the script has been deprecated by Atlassian.
|(DataSource) Added pagination support to scripts; updated request headers.
Note: As discussed in New LogicModules, LogicMonitor portal monitoring has been significantly enhanced with the release of six new LogicModules.
|(DataSource) Monitoring of the ExpressRoute virtual network gateway type has been removed from this DataSource and is now performed by the newly released Microsoft_Azure_ExpressRouteVirtualNetworkGateway DataSource.
Note: Some instances may be deleted upon update; however, impact should be minimal as it is unlikely that these instances were collecting valid or complete data.
|(TopologySource) Updated to not link Aruba devices where the MAC has the same OUI as the LLDP device id.
(PropertySource) Added safe navigation to allow for missing SNMP sysinfo which was causing some devices to not be mapped correctly.
|(3 DataSources) Added handling for capitalized sensor state values returned by ESX 7.0 and above.
|Minor update made to an assortment of DataSources:
|(18 DataSources) For one or more datapoints contained within these DataSources, fixed incorrectly worded alert messages.
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.
|End of Support Date
LogicModules Deprecated in v.145
|(1 DataSource) Converted to a scripted DataSource and uses an additional OID to resolve duplicate wildvalues.
Liebert Power lines
Liebert Temperature probes-
Liebert UPS Temperature probes-
|(3 DataSources) Rewrote DataSources as scripted SNMP; merged monitoring of temperature and UPS temperature probes into a single DataSource; added new power and voltage metrics for power lines monitoring; fixed an incorrect filter for power lines.
|(1 DataSource) LogicMonitor released five new DataSources that provide 15 additional datapoints and group related metrics into separate DataSources, making it easier to hone in on specific aspects of your portal. For more information, see LogicMonitor Portal Monitoring.
LogicModules Previously Deprecated (over past five versions)
|(1 DataSource) It has been determined that all data gathered by this DataSource is being reported more robustly through the existing NetSNMPCPUwithCores and NetSNMP_Memory_Usage DataSources, making it redundant and unnecessary.
|(4 DataSources)General cleanup of DataSources that are not widely used and no longer work correctly.
|(1 DataSource) Active Discovery and data collection methods were converted from SNMP to script to improve overall efficiency.
|(1 DataSource) “VMware” was removed from the DataSource name as the backups are not VMWare specific.
|(1 DataSource) Windows SNMP support has been deprecated by Microsoft since Server 2012 R2. As a result, this DataSource does not collect reliable data for Server 2016 and above.
Cisco AIP SSM Memory Pools-
|(1 DataSource) The replacement DataSources offer a scripted SNMP version that returns accurate values. If you were previously using the now-deprecated DataSource, it can be deleted as it was providing invalid data.
|(1 DataSource) Uses a deprecated API. It is strongly recommended that this LogicModule be deleted and the replacement LogicModule be used.
|(1 DataSource) The replacement DataSources filter out instances to allow for separate DataSource monitoring of memory, flash storage, and standard storage.
|(1 DataSource) Did not provide accurate/useful data and can be deleted; the existing Linux_SSH_ServiceStatus DataSource has been retooled in v.141 to perform the same function.
|(1 DataSource) The replacement DataSource offers several advantages including (1) the use of the more widely supported nstat (part of iproute2) command and netstat as fallback if nstat is not available and (2) additional monitoring for packet, datagram and error related metrics
|(1 DataSource) Changed the collection method from standard SNMP to scripted SNMP to properly handle the units returned for the VolFreeSize and VolTotalSize datapoints. In the now-deprecated version, these datapoint calculations were failing if the returned values were not expressed as terabytes leading to data misrepresentation.
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.