LogicMonitor seeks to disrupt AI landscape with $800M strategic investment at $2.4B valuation to revolutionize data centers.

Learn More

EA Collector – 29.109

Updates Fixed an issue in EA 29.107 where upgrading failed if the Collector is running as root. Upgrading from EA 29.107 Note: This issue only applies to upgrades if the Collector is running as root. To upgrade from EA 29.107 if you’re running it as root, you’ll need to first go to the LogicMonitor portal … Continued

EA Collector – 29.108

Updates Added integration support for external credential management using CyberArk Vault. See Credential Vault Integration for the LM Collector.

EA Collector – 29.107

Updates Fixed various issues to improve performance for LM Logs and Syslog collection. Fixed an issue for NetFlow NBAR that caused the Collector memory to max out. Known Issues EA Collector 29.107 fails to upgrade if the collector is running as root. This has been fixed in EA Collector 29.109. See Release Notes. Downgrading to … Continued

EA Collector – 29.106

Important: This Collector version fixes the known issue present in versions 29.101 through 29.105 that was resulting in resources with heartbeats to be incorrectly marked as dead/down. Enhancements/Updates Added JMX metrics for LM Logs To better support LM Logs, two new settings have been added to the Collector agent.conf file: lmlogs.syslog.hostname.format – To accommodate syslog … Continued

EA Collector – 29.105

Known issues in this version: An issue is resulting in resources falsely appearing and alerting as dead/host down when they aren’t actually down. As of now, there is no workaround (other than downgrading), but we are actively working on it. LogicMonitor’s default use of SSE (Standalone Script Engine) to execute script DataSources is causing some … Continued

EA Collector – 29.104

Known issues in this version: LogicMonitor’s default use of SSE (Standalone Script Engine) to execute script DataSources is causing some LogicModules (notably Cisco Meraki DataSources) to fail to execute properly on this Collector version. As a workaround, you can disable SSE in the Collector’s configurations by updating the value of the groovy.script.runner setting to “agent”. … Continued

GD Collector – 29.003

Enhancements/Updates Upgraded the JRE to Amazon Corretto 11.0.8.10.1 Fixes Fixed an issue where PropertySource timeouts weren’t set until after the task was complete, causing them to improperly timeout. Fixed a buffer overflow bug in sbproxy that would cause it to restart when trying to process some Windows Event Log EventSource events (only applicable to Windows … Continued

EA Collector – 29.102

Known issues in this version: An update of the log4j Collector JAR (from 1.2.17 -> 2.13.2) is causing Cisco_IOS and Cisco_NXOS ConfigSources to fail. New versions of these ConfigSources are available that resolve this issue. (Update: This issue is resolved in EA 29.106) LogicMonitor’s default use of SSE (Standalone Script Engine) to execute script DataSources … Continued

EA Collector – 29.101

Known issues in this version: LogicMonitor’s default use of SSE (Standalone Script Engine) to execute script DataSources is causing some LogicModules (notably Cisco Meraki DataSources) to fail to execute properly on this Collector version. As a workaround, you can disable SSE in the Collector’s configurations by updating the value of the groovy.script.runner setting to “agent”. … Continued