LogicMonitor v.154 is scheduled to roll out to customer portals from June 21 through June 30.
Updated on June 30, 2021
- FIXED an issue that caused data latency when monitoring AWS environments.
- General Updates: Added a details panel to the LM Logs table to show log messages and alerts information, added support for several AWS services in LM Logs, fixed an issue with data collection in Cloud Monitoring, and more.
- Updated Monitoring: New and updated LogicModules to monitor Microsoft SQL Server database status and health, track the throughput of Direct Connect Virtual Interfaces, and support topology mapping for Intermediate System to Intermediate System (ISIS).
- Looking Ahead: Push Metrics API, OpenMetrics DataSource, and Distributed Tracing goes GA on June 30th. Find out more!
- FIXED an issue with Local Collector assignment to display Collector type and Collector Group properly.
- FIXED an issue in Cloud Onboarding and Management pages for Azure to make sure all subscriptions are shown.
- FIXED an issue where data collection was not happening because users did not have the correct account-level permissions for AWS devices. Now permissions are verified and users will be notified of potential issues.
- ADDED support for external credential management using CyberArk Vault beginning with EA Collector – 29.108. The vault integration is available as an open beta with support for more vaults to follow in upcoming releases. For more information, see Credential Vault Integration for the LM Collector.
- FIXED an issue where cleared alerts were not being recorded in integration logs for deleted instances.
- ADDED support for several AWS services, including CloudFront standard access logs, Kinesis Data Stream API calls, Kinesis Firehose API calls and Error logs, and ECS API calls.
- CHANGED the Logs table to match other tables in LogicMonitor pages. The new UI provides dynamic, resizable columns, and a new details panel to view log messages and alerts information.
- FIXED an issue where deleting an alert condition from a log processing pipeline disabled the pipeline.
- ADDED the NetFlow Collector ID to the Resource properties information view.
- CHANGED the SLA Widget and Report to include the thousandths decimal place, for example: 99.999%.
- FIXED an issue where Resources and Resource Groups with instance names containing special characters did not populate graphs in HTML or PDF.
- ADDED the ability for users to select more than one Edge Filter in one flow when defining Alerts in Topology.
- CHANGED two-factor authentication (2FA) settings to make mobile number a required field.
- FIXED an issue where the Graph Widget was showing the wrong Y-axis values for Line graphs.
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.
|(1 PropertySource, 1 TopologySource) Topology mapping support for devices that support the Intermediate System to Intermediate System protocol (ISIS).|
|AWS_DirectConnect_VirtualInterface||(DataSource) Tracks throughput of Direct Connect Virtual Interfaces.|
|Microsoft_SQLServer_AlwaysOnDatabaseStatus||(DataSource) Gathers metrics for and alerts on synchronization health, synchronization status and overall database status.
See Updated LogicModules: Microsoft_SQLServer_AlwaysOnAvailabilityGroups, Microsoft_SQLServer_AlwaysOnAvailabilityReplicas, Microsoft_SQLServer_AlwaysOnDatabaseReplicaCluster, Microsoft_SQLServer_AlwaysOnDatabaseReplicas.
|addCategory_Cisco_APIC||(PropertySource) Ensure manually set API port is converted to an integer.|
|addCategory_MongoDB||(PropertySource) Probe provided ports before attempting a connection. Ensure connections are closed before script exit. Ensure wildvalues and wildaliases are properly sanitized.|
|addCategory_NetApp||(PropertySource) Reverted regression that caused script to fail when SSL was not configured for the API endpoint.|
|addCategory_TopoSwitch||(PropertySource) Remove filter for Cisco ASR devices.|
|addCategory_WindowsFailoverCluster||(PropertySource) Added ability to recognize SQL Availability Group clusters. IP addresses will now work with remote domains.|
Cisco DNAC Issues
|(3 DataSources, 1 EventSource, 2 PropertySources, 1 TopologySource) Prevent script failure when the “proxy.enable” property is not set. Fix invalid conditional statements in ERT generation for Cisco_DNAC_Devices. Fix invalid appliesTo category for addERI_Cisco_DNAC and Cisco_DNAC_Topology.|
|(2 DataSources) Account for multiple threshold values being set. Use the combination of both threshold alert values (lowest value for both, as 2 represents false and 1 represents true in the OID), which will result in the threshold_evaluation datapoint returning 1 if either of the thresholds get broken.|
|Cisco_IPSec_PolicyBasedTunnels||(DataSource) Fixed wildvalue sanitation to ensure wildvalues are consistent across active discovery and collection.|
|(4 DataSources) Will now alert if the ConnectionStatus is 0(disconnected) rather than on a change in connection status.|
|Dell_DRAC_DriveStatus||(DataSource) Update complex datapoint expression for AlertFilter to prevent generating alerts for “read-only” and “not RAID capable” statuses.|
|(14 DataSources) Replaced deprecated Groovy HTTP library with URL library. Ensure cluster names are properly encoded in request URLs. Remove unused null checks.
Note: For DellEMC_XtremIO_DAEPSU, ensure correct status code is returned for the powerFailure datapoint
|F5_BigIP_HA||(DataSource) Used correct OIDs for sync and failover status.|
|HP_3PAR_Disk||(DataSource) Ensure that graphs representing byte values are scaled properly.|
|HP_MSA_Ports||(DataSource) Updated incorrect status code mapping for the status datapoint and added missing “Unknown” status to both status and health datapoints. Note that historical data collected by prior versions of the module may be inaccurate.|
|(DataSource) Update connection logic to attempt connections with SSL enabled before falling back to an insecure connection.|
|(DataSource) Update AppliesTo to avoid applying the module on newer collectors, which should be using the newer JMX based module (LogicMonitor_Collector_BufferDataReporterLatencyJMX).|
|LogicMonitor_Collector_LMLogs||(DataSource) Fixed regression in previous version by removing alert for the SizeOfBigQueue datapoint. Populated missing datapoint descriptions.|
|Meraki_Cloud_Topology||(TopologySource) Query different endpoints depending on the presence of either a network id and/or an organization id. Add check for empty hostnames. Add caching support.|
|(2 DataSources) Updated collection interval to 30 minutes.
Note: For Microsoft_Azure_BackupJobStatus : Added healthStatus datapoint to track the overall health of the backup, based on backupStatus and protectionStatus.
|Microsoft_Azure_WebApplication||(DataSource) Re-added CpuTime datapoint which was accidentally removed in a previous release.|
|(4 DataSource) Updated SQL statements used in scripts. Updated AppliesTo function to ensure that modules are only applied if the “WSFC_VNN” category associated with Windows cluster VNNs is set.
Important: Requires addCategoryWindowsFailoverCluster v.1.3.0 or above.
AvailabilityGroups: Changed instance names, note that this may wipe all current instances and their associated historical data. Add alerting on the SyncHealth datapoint. Added failureConditionLevel datapoint. Removed primaryRecoveryHealth and secondaryRecoveryHealth datapoints. Removed auto.sql_instance instance property.
AvailabilityReplicas: Increase active discovery interval. Removed alerting. Removed auto.sql_instance instance property.
DatabaseReplicaCluster: Increase active discovery interval. Updated SQL query to remove duplicate data gathering. Adjusted alert threshold for is_failover_ready datapoint. Added alerting to is_pending_secondary_suspend datapoint. Ensure is_database_joined returns the correct status code.
DatabaseReplicas: The SQL Node names are now included in the wildvalues, note that this will wipe all current instances and their associated historical data. Enabled automatic instance deletion. The database_state, synchronization_health, synchronization_state datapoints have been moved to the new Microsoft_SQLServer_AlwaysOnDatabaseStatus DataSource.
|(3 DataSources) Append used port to wildvalue and wildalias.
Note: This will delete existing instances and their associated historical data.
|Oracle_Database_Troubleshooter||(DataSource) Moved the entire solution message to the auto.oracle.solution instance property.|
|PaloAlto_GlobalProtect_Sessions||(DataSource) Ensure wildvalues are properly sanitized.|
|SNMP_Network_Interfaces||(DataSource) Updated interface filtering to only filter interface types filtered in the snmp64If- module. Fixed LastChange metric output, which was previously returning invalid data. Fixed parsing for flap status, was previously only returning false. Account for decimal points in raw interface speeds. Fixed sanitization of the interface alias and description. Do not set “null” for the interface alias or description. Account for counters wrapping for the InOctets and OutOctets datapoints. Use concurrent SNMP collection for Juniper devices to minimize CPU utilization, can be overridden with the “interface.snmp.method” property (accepts: “walk”, “get”, “getconcurrent”. Defaults to “walk”). Sanitize imported host properties. Add timeout for interface extraction. Only set the “auto.interface.speed” property if a valid interface speed is returned. Retry failed SNMP walks and gets. Removed complex datapoints with invalid expressions, InOctets95Percentile and OutOctets95Percentile, and moved percentile calculations to graph virtual datapoints..|
|PSophos_XG_Licenses_v18+||(DataSource) Fixed incorrect alert threshold operators.|
|VMware_ESXi_DatastoreCapacity||(DataSource) Updated description of the DiskProvisioned datapoint.|
|VMware_vCenter_DatastoreCapacity||(DataSource) Reverted a wildalias change introduced in v153.
Note: Any instances generated due to the updated wildaliases will not be automatically deleted upon import of the newest version.
|(4 DataSources, 1 PropertySource)
Modules now support the optional “velo.enterpriseIds” property to either limit the monitored enterprise IDs or specify enterprise IDs in the event that active discovery fails to automatically discover enterprise IDs, if unspecified the modules will attempt to discover and monitor all enterprise IDs, a comma-separated list of enterprise IDs or a single ID is expected for the property. Added fallback API endpoint for enterprise ID discovery. Wildvalues now have the enterprise ID prepended, which will cause new instances to be created and historical data for old instances to be deleted. Attempt to authenticate with the enterprise login API endpoint and fallback to the operator login endpoint on failure. Ensure that requests that include time intervals use UTC time as expected by the API and determine intervals based on polling interval rather than a hardcoded value. Update authentication code to detect responses with HTML login pages, token errors with 200 response codes and attempt to reauthenticate when encountering an expired token. Add proxy support. Add more descriptive error and debug messages.
EdgeHealth: Removed the UptimeSeconds datapoint.
EdgeLinkHealth: Added STANDBY status code to linkEffectiveState.
|Details||End of Support Date|
|(2 DataSources) No longer in use for Topology generation.||2021-08-27|
|(DataSource) Provides the same data as the CPU Cores- DataSource.||2021-08-27|
|(2 DataSources) Unable to report consistent data across devices/instances.||2021-08-27|
|(DataSource) Did not provide useful data. It is recommended that JobMonitors be used to monitor crontab entries.||2021-08-27|
|(DataSource) Change active discovery and collection to batchscript. Try and handle renamed or missing instances.||2021-07-02|
For the list of LogicModules deprecated over the past five releases, see the support article Deprecated LogicModules.
In this section you will find announcements about upcoming beta features, updates about ongoing beta features, and information about the end-of-life of existing features.
LogicMonitor’s new APM capabilities will be available to a limited number of customers starting on June 30th. You will be able to take advantage of Distributed Tracing, Push Metrics API, and OpenMetrics DataSource Wizard to associate application metrics and traces with your infrastructure for complete coverage across your entire stack.
LogicMonitor’s distributed tracing functionality will be generally available soon! With this new distributed tracing capability, you will be able to forward traces from your instrumented applications to LogicMonitor. This will enable you to see end to end traces as they flow through the services in your environment (from a new Traces page in LogicMonitor), presented with contextual metrics and logs to enable faster troubleshooting and more proactive identification of performance bottlenecks.
Push Metrics APIs
The Push Metrics API is now available for use in production environments, but the feature must be enabled for use.Push Metrics allows you to send metrics directly to the LogicMonitor platform via a dedicated API, removing the need to route the data through a LogicMonitor Collector. Once ingested, these metrics are presented alongside all other metrics gathered via LogicMonitor, providing a single pane for metric monitoring and alerting.
OpenMetrics DataSource Wizard
The OpenMetrics DataSource Wizard. The wizard requires the EA Collector 30.100 or later. The wizard can be used to quickly load OpenMetrics (Prometheus exposition format) data from a provided URL endpoint and create a datasource for ingesting the data into your LM account.
Sunset of the RPC API
We have decided to focus on improving the LogicMonitor Rest API, which has higher security standards and integration capabilities that are more in-line with our future development goals. This means that we are preparing to end support for the RPC API with the upcoming release of LogicMonitor v.156.
If you are using the RPC API for Ansible, reach out to Support for guidance on migrating playbooks to the REST API.