EA Collector – 29.105

Last updated on 15 October, 2022

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 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”. See Editing the Collector Config Files for instructions on editing Collector configurations.

Note: Both of these issues are resolved in EA 29.106.


  • A new DataSource named LogicMonitor_Collector_BufferDataReporterLatencyJMX for monitoring latency of the Collector buffer data reporter (via JMX) has been released to specifically work with Collector versions 29.105 and higher. The existing DataSource (LogicMonitor_Collector_BufferDataReporterLatency) is still required for versions 29.104 and lower. LogicMonitor recommends that, even if you’re not yet using Collector version 29.105, you still import this new DataSource. The newer DataSource will not associate until the Collector version is updated to 29.105 or higher at which time it will automatically associate, ensuring a smooth monitoring transition. At that time, the older DataSource will cease to function.


  • LM Logs
    • Previously, syslog events without a hostname header were dropped by the Collector for the LM Logs syslog integration. For these log events, the Collector will now use the socket IP rather than dropping the events (which is consistent with the Syslog EventSource logic). This is particularly relevant for syslog events from Cisco devices.
    • Added support for parsing RFC 3164 and RFC 5424 formatted log events. Previously, the Collector failed to parse the hostname for these formats.
  • Several new properties, listed next, are now available to tune requests for Web Checks. These properties all default to 30 seconds and all support an acceptable value range between >0 and <=60.
    • website.http.client.so.timeoutInSec (socket timeout in seconds)
    • website.http.client.connect.timeoutInSec (TCP connection timeout in seconds)
    • website.http.client.read.timeoutInSec (read timeout in seconds)


  • Fixed issue with syslog collection from Cisco devices.
  • Fixed issue preventing ingestion of flow sampling rate when sent in an optional template, which resulted in NetFlow traffic underreporting.
  • Fixed a bug that would cause JDBC Active Discovery to ignore the “Port # List” field.
  • Fixed an issue where configuration monitoring would change line ending characters.

In This Article