v.157 Release Notes

Last updated on 15 October, 2022

LogicMonitor v.157 is scheduled to roll out to customer portals from August 23 through September 1.


  • Feature Highlights: New Logstash monitoring, support for one year log retention with LM Logs Enterprise, topology visualization for relationships between AWS services, and support for customizing Azure Monitor datapoints.
  • General Updates: Added access to the new design of the Alerts page, mapping of AWS Trusted Advisor severity in the EventSource, updates to Distributed Tracing, and more.
  • Updated Monitoring: New LogicModules to monitor Logstash metrics, provide topology support for AWS services, and more.

Feature Highlights

Logstash Monitoring is now available

You can now monitor your Logstash plugins, pipelines, and events as well as JVM and health and performance metrics to ensure this critical component of your observability infrastructure is always up and running. If you’re already sending Logstash logs to LM Logs using our output plugin, these new LogicModules will provide added visibility into your Logstash metrics. See New LogicModules.

LM Logs Enterprise supports one year log retention

With LM Logs Enterprise, you can retain logs for one year of hot storage. This means that you can instantly access and search logs and log anomalies throughout the one year time period. The alternative is 30 days of log retention with LM Logs Pro. For more information, contact your Sales representative.

Topology visualization between AWS services

We now display the topology relationships between monitored AWS service, such as EC2 to  EBS or AutoScaling Group to EC2. You may find this useful for visualizing your complex AWS environment and determining the impact of issues, as alert status is overlaid for each resource.

Customizing Azure Monitoring datapoints

If you have LogicMonitor DataSources that use the “Azure Insight” collection method, you can now customize the datapoint definition to include Azure Monitor dimension metrics. See Customizing Azure Monitor Datapoints.

General Updates


  • FIXED an issue where the LogicMonitor portal incorrectly reported that a job completed at the current time, when the job may not have completed. This is a partial fix to correct finish times for one-month old data and new jobs. Our Support team will work with users who are facing this issue. Note: In an upcoming fix, users will receive alerts if a job takes too long to complete or is terminated.
  • ADDED the option to choose between two versions of the Alerts page. “Alerts (Legacy)” is the current version of the page, while “Alerts (Stable)” will direct you to an updated design of the Alerts page. The stable version displays all the filter options in a dropdown except for the severity toggles.

Cloud Monitoring

  • ADDED the option to map the severity from AWS Trusted Advisor in the AWS Trusted Advisor EventSource alert level definition. When setting “Alert Level for Matching Events” in the EventSource definition to “Mapped from AWS Trusted Advisor”, the severities for alerts are mapped from the respective AWS Trusted Advisor events.
  • ADDED the Device Uptime widget for Azure VMs.
  • FIXED an issue where backup properties for Azure VMs weren’t discovered if the backup vault and VM were in different resource groups. This prevented proper monitoring via the Azure VM Backup DataSource.
  • FIXED the efficiency of the permission test that occurs when Azure subscriptions are added, enabling selection of one or more subscriptions at once.

Distributed Tracing

  • ADDED the ability to view trace data older than the past day. The retention period of trace data is two weeks. Users can select a datetime range within a two week window, and the maximum range selection allowed is one day.
  • ADDED a new DataSource for service namespaces to monitor duration, error, and span count statistics for traces across services in the namespace.
  • FIXED graphs for resource and service level trace metrics (Push API-based DataSource) to display metrics with different units in different graphs.

LM Logs

  • ADDED support for AWS RDS VPC Flow Logs collection.

LM Service Insight

  • ADDED information about member instance data to service alerts, making it easier for you to drill down from the aggregate value that triggered the alert and view the underlying instances that contributed to the alert.
  • FIXED for cases involving delayed Cloud data collection, service aggregation wasn’t working well because member values weren’t received in time. We’ve made the tolerance period for aggregation more flexible to account for this scenario.


  • ADDED support for a split wildcard search to “Filter Metrics” on the Load Metrics page of the wizard. This allows users to search for metrics for processing by combining multiple wildcard searches into one. For example, you can search for user can search for text1*text2. This will find any metric containing text1 and text2. This is helpful to find a metric that contains a text string along with a related label or label value quickly

Push Metrics API

  • ADDED support for creating a single instance DataSource via the Push Metrics API. When the new flag singleInstanceDS is set to true, the DataSource that is created will have only one instance associated with it


  • FIXED the SUM function in the Resource Metric Trends Report now correctly calculates the total number for reporting periods greater than 24 hours.
  • FIXED the SLA Reports unavailable time when “exclude SDT” is selected to match expected values.
  • FIXED an issue where Dashboard Reports were not generating data when NetFlow Widgets are added.

Rest API

  • FIXED API calls to the PATCH report/reports/{id} endpoint to not override the Scale Units and Report Access fields to blank, and added the same fields to be available to GET requests.


  • FIXED the Roles page to correctly label Audit Logs (previously it was Access Logs).


  • ADDED a Clear button to reset filtering options.
  • REMOVED the Filter menu and moved the Edge Filter menu so that it is always visible.

User Interface

  • FIXED the persistence of “Exclude SDT periods” setting for SLA dashboard widgets.

LogicModule Releases

New and updated LogicModules are available for you to import from the LogicMonitor Public Repository. This section lists the LogicModules that are new in this release, updated in this release, or will be removed in a future release. Changes related to the LogicModule feature will be listed under General Updates.

New LogicModules

LogicModule Name Details
(6 TopologySources)
Provides topology support for the following AWS services: WorkSpaces, MSK, RDS, Elastic Beanstalk, Auto Scaling, EC2, EBS and ELB.
(1 ConfigSource, 5 DataSources, 1 PropertySource)
Tracks installed plugins, pipeline, events, configuration, JVM and health and performance metrics via the Logstash API.

Updated LogicModules

LogicModule Name Details
Arista_Interface_Queue (1 DataSource)
Updated instance filtering to omit types of interfaces that do not return network traffic data
AWS_DMS_Tasks (1 DataSource)
Removed upper bound limit on the memoryUsage datapoint and updated description to reflect that the value includes swap.
(8 DataSources, 1 PropertySource)
Ensures the “apic.api.port” property is converted to an integer before being used in scripts.
Cisco_APIC_Interfaces (1 DataSource)
Added multi-threaded discovery and collection. The number of threads used can be changed by setting the “apic.api.threads” host property, defaults to 4. This is meant to handle large numbers of interfaces quickly.
Cisco_CPU_Usage (1 DataSource)
Ensures that accurate instance names are used. Will result in recreation of instances with inaccurate names and loss of the associated historical data.

Note: To protect historical data, the old DataSources should be renamed and disabled before the updated module is imported. Added new datapoints for memory statistics. Please reach out to Support if you need help with this.
Cisco_CUCM_FileCache (1 DataSource)
Implemented locking to prevent multiple hosts from ingesting the same call records. Any additional record ingestion attempts by the same host within 30 seconds will be blocked, as well as any ingestion attempts originating from a different host within 24 hours of the last ingestion.
Cisco_DNAC_Devices (1 DataSource)
Prevents failed ERI generation from causing Active Discovery to fail.
Cisco_Transceiver_SensorsCLI (1 DataSource)
Makes use of SNMP interface information if available. Replaced the Expect library with SSHJ and added support for key based authentication.

Requires EA Collector 28.606 or higher.
Citrix_Netscaler_FullBackup (1 DataSource)
Allows for spaces in filenames.
CommVault_Storage_Pools (1 DataSource)
Fixed incorrect megabyte to byte conversion.
EMC_VMAX_RDFDirector_V8.3 (1 DataSource)
Fixed post-processor parameter for the SyscallRemoteDirCount datapoint.
F5_BigIP_VIP_Statistics (1 DataSource)
Increased timeouts on snmp walk. Cleaned up collection script and better handle partial collections.
(3 DataSources)
Updated the discovery interval.
(3 DataSources)
Tracks duration, operation and error count both globally and per service, as well as trace count per root service.
LogicMonitor_Collector_TLSVersion (1 DataSource)
Updated AppliesTo function to match other Collector modules.
(2 DataSources)
Monitors Azure Virtual Desktop session hosts and session host pools.
Nimble Volume Usage (1 DataSource)
Converts Active Discovery and collection to scripted to prevent instance deletion resulting from discovery failures.
SilverPeak_System_ActiveAlarms (1 DataSource)
Updated wildalias to use a unique OID.

Note: All instances will be replaced as a result of this change which will result in historical data loss, though previous historical data should be considered unreliable.
Ubiquiti_UniFi_Sites (1 DataSource)
Ensure proper fallback to the legacy API endpoints when encountering a 404 response code when querying the new endpoints.
Veeam_BackupAndReplication_Jobs_Copy (1 DataSource)
Implemented a more reliable method to determine the most recent execution of each copy job.
VMware_ESXi_HostStatus (1 DataSource)
Fixed status code number in the description of the RebootRequired datapoint.
AWS RDS PI Top 2 User IDs
AWS RDS PI Top 5 Tokenized SQL Statements
AWS RDS PI Top 10 SQL Statements
(3 EventSources)
Fixed module metadata.
(2 PropertySources)
Group CISCO CUCM PropertySources.
addCategory_StatusPageIO_Key (1 PropertySources)
Fixed filtering of private IP ranges. Fixed key extraction logic to attempt to extract the key from the summary.json endpoint before parsing the raw response.
(3 PropertySources)
Blocks Cisco ASA MAC addresses.
addERI_Linux (1 PropertySources)
Blocks MACs associated with VMware VMs and Riverbed appliances.
Device_BasicInfo (1 PropertySources)
Converts MAC addresses returned in binary format to hexadecimal format.

Deprecated LogicModules

This table lists LogicModules that we are deprecating in this release. This means that these LogicModules will be removed in a future release. If available, a replacement LogicModule is listed. For the list of LogicModules deprecated over the past five releases, see the support article Deprecated LogicModules.

LogicModule Name
Details End of Support Date

(1 DataSources) Deprecated module was querying OID that returns invalid data. New module tracks queries, responses, and referrals per zone. 2021-11-10

(8 DataSources)
Created excessive instances.

(3 DataSources)
Overlap between Cisco_Nexus and Cisco DataSources. Deprecated duplicate modules to prevent double monitoring or alerting.

Metrics for Cisco_Nexus_CPU_Memory are present in the latest version of Cisco_CPU_Usage. Metrics for Cisco_Nexus_Fan and Cisco_Nexus_FRU_Status are present in Cisco_FRU_Power.
In This Article