Join fellow LogicMonitor users at the Elevate Community Conference and get hands-on with our latest product innovations.

Register Now

Resources

Explore our blogs, guides, case studies, eBooks, and more actionable insights to enhance your IT monitoring and observability.

View Resources

About us

Get to know LogicMonitor and our team.

About us

Documentation

Read through our documentation, check out our latest release notes, or submit a ticket to our world-class customer service team.

View Resources

Collector Release Notes Timeline

Last updated on 27 March, 2024

December 09, 2020

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 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.

Notes

  • 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.

Enhancements/Updates

  • 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)

Fixes

  • 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.

November 10, 2020

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

    Note: This issue is resolved in EA 29.106.

Enhancements/Updates

  • Support for LM Logs has been added.
  • Upgraded Amazon Java Corretto to 11.0.9.11.1 (October 2020 quarterly update). The Windows Collector has been upgraded to 11.0.9.11.2, which includes a Windows-only fix in addition to the quarterly update.
  • Support for the Suppress duplicate EventIDs even when messages differ option has been added. This option resides on the configuration dialog for Windows Event Log EventSources and allows you to override the default suppression that takes place for events with identical EventIDs.
  • Upgraded included JBoss Java libraries from 2.0.0 to 2.0.10.
  • The !splist debug command now shows the name of the PropertySource in addition to its ID.
  • Removed unused syslog related directives from the agent.conf file.
  • Enhanced logging for ignored received syslog messages.
  • Performance improvements for Windows Event Log EventSources.
  • Various minor security improvements.
  • Updated the default value of the collector.batchscript.threadpool configuration to 20 threads to support LogicMonitor’s increasing reliance on BatchScript in DataSources.
  • Implemented aggregation logic to preserve remaining network flow traffic as “remaining traffic” to persist values to equal bandwidth records.

Fixes

  • Excessive DNS lookups are now avoided through the utilization of the local cache with LM Logs.
  • An issue causing Script EventSources to not properly report events when running in the SSE has been resolved.

September 29, 2020

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 Collectors).

Known issues

  • There is an issue where the installer may not apply the proxy settings input. This only affects the installer. If you already had the properties set they should continue to still work. The workaround is to install another version.

September 15, 2020

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 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.

Enhancements/Updates

  • Adjusted the output text width of Collector debug information (as displayed in various locations in the UI such as Collector Debug Facility or test script), making Java exception text easier to read.
  • IPFIX flow records lacking required fields are now properly discarded.
  • VMware detection now correctly differentiates between vCenter, ESXi, and workstation.
  • The Collector installer now depends on `od` instead of `xxd`, which will fix issues installing the Collector on RHEL.
  • We’ve removed the following Java libraries from the Collector:
    • Dom4j-1.6.1.jar
    • Commons-ssl-1.0.jar
    • Commons-httpclient-3.1.jar
  • We’ve updated the following JARs:
    • jackson-databind 2.8.11.3 -> 2.11.0
    • jetty-server 8.1.12 -> 9.4.3.0
    • jetty-http 8.1.12 -> 9.4.3.0
    • jetty-util 8.1.12 -> 9.4.3.0
    • commons-beanutils 1.9.2 -> 1.9.4
    • log4j 1.2.17 -> 2.13.2
    • bcprov-jdk15on 1.60 -> 1.66
    • jboss-remoting 5.0.0 -> 5.0.17
    • commons-io 2.2 -> 2.6
    • fastjson 1.2.57 -> 1.2.62
    • commons-codec 1.1.0 -> 1.14

Fixes

  • Fixed issue causing sbproxy to continuously restart on Windows Collectors when collecting Windows Event Logs.
  • Fixed issue where NetScan timeout in seconds was interpreted as milliseconds, causing unexpected timeout conditions.
  • Docker Collector installation now works for EA.

August 17, 2020

GD Collector – 29.002

Collector version GD 29.002 fixes an issue causing web page collection tasks to get held up and consume CPU.

August 06, 2020

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

    Note: This issue is resolved in EA 29.106.

Enhancements

  • Upgraded the JDK to Amazon Corretto 11.0.8.10.1.
  • NetScan Groovy scripts are now run in the SSE.
  • NBAR slots support for Direction, IPv6, Application.
  • Linux Collector uninstaller will remove its modifications to /etc/sudoers, stop the service, and remove the service symlink.

Fixes

  • Fixed issue that would cause PropertySource output to be parsed incorrectly if more than one property was to be set.
  • Fixed issue in 29.100 on Windows where custom install path was ignored.
  • NetFlow collection properly discards negative values.

July 16, 2020

GD Collector – 29.001

Collector version GD 29.001 fixes an issue in GD 29.000 that prevented the successful upgrade to GD 29.000 from an EA 28 version (28.400 – 28.607) of a Linux Collector running as a non-root user.

July 07, 2020

GD Collector – 29.000

Collector version GD 29.000 incorporates all enhancements and fixes found in M/GD 28.005, as well as EA 28.xxx (28.100, 28.200, 28.300, 28.400, 28.500, 28.501, 28.600, 28.601, 28.602, 28.603, 28.604, 28.605, 28.606, 28.607).

Next we’ve listed a few highlights across the various releases that GD 29.000 rolls up. For a complete list, visit the individual release notes pages for the various releases.

  • Amazon JDK 11 (replaced Oracle JDK 8)
  • SHA2 support for SNMP v3
  • New SSHJ library
  • Run as non-root/non-admin
  • Bourne shell-based installer (replaced Perl-based installer, for portability)
  • EventSource testing
  • Various CPU and memory efficiency improvements

June 24, 2020

EA Collector – 29.100

Enhancements:

  • Introduces the Collector Script Cache to allow caching of things like session tokens between collection intervals, without dumping things on the filesystem.
  • Groovy scripts for PropertySources and TopologySources now run in the SSE.
  • The xxd dependency for Linux Collectors is now shipped with the Linux Collector. This was unavailable in many Linux distributions by default.
  • Systemd unit file is now stored in /etc/systemd/user for non-root installations.
  • Introduces Extra Large (XL) and Double Extra Larger (XXL) size collectors for 16 GB and 32 GB of RAM. See Collector Capacity.
  • Improvements made to prevent dead, timed out JDBC tasks from stacking up.
  • Improved SSE error messages.
  • NetFlow exports received over UDP can now be processed in a multi-threaded manner on the Collector. Previously, processing was limited to a single thread.
  • The !http debug command now supports timeout, HTTP version, header, and body arguments to facilitate troubleshooting.
  • Instance-level property (ILP) values supplied in Active Discovery scripts no longer require URL encoding. Previously, reporting a character such as “%” would cause parsing to fail.
  • TinyRADIUS Java Library is now included. LogicModules that utilize these to test RADIUS login will be available in a future release.
  • Augur Systems’ TACACS Java Library is now included. LogicModules that utilize these to test TACACS+ login will be available in a future release.
  • Upload scripts are now sent to agent/local/bin instead of agent/lib.
  • Custom JARs should now be placed in agent/local/lib instead of agent/lib.
  • Added scripts to allow the migration of a Collector running as root or Administrator to a non-root or non-Administrator user.
    • Windows: agent/bin/windows/updateToNonAdmin.ps1
    • Linux: agent/bin/linux/updateToNonRoot.sh
  • Added a warning that installing the Collector to run as a non-root user on Linux requires editing /etc/sudoers. This dependency is targeted for removal in a future version.

Fixes:

  • Log indicating absence of agent/conf/agent.conf.local is now WARN level instead of ERROR.
  • Improved the error message when failing to install on a non-x86, 64-bit OS. Previously, we indicated that failure was because the OS was not 64-bit when, in actuality, it was because we don’t support ARM64, for example.
  • Fixed issue mentioned in 28.005 notes, where Upload Scripts would fail if they didn’t print out a newline at the end of the collection script.
  • Fixed issue where long debug commands were unrecognized as valid commands
  • Fixed issue in which the TaskCountInQueue datapoint found in the LogicMonitor_Collector_ConfigCollectingTask DataSource would return negative values.
  • Fixed issue where debug commands could not handle special characters

May 28, 2020

EA Collector – 28.607

Enhancements:

  • Updated the Collector JRE to Amazon Corretto version 11.0.7.10 (April 2020 patch)

Fixes:

  • Fixed an issue where AES-256 SNMPv3 was not working with some Cisco devices
1 2 8 9 10 11 12

Start Your Trial

Full access to the LogicMonitor platform.
Comprehensive monitoring and alerting for unlimited devices.