Collector Release Notes Timeline

Last updated on 27 March, 2024

August 08, 2019

EA Collector – 28.602

Fixes:

  • Fixed a bug that would cause JDBC Active Discovery to ignore the “Port # List” field.

July 24, 2019

EA Collector – 28.601

Fixes:

  • Fixed issue with watchdog that would prevent the collector configuration from being edited in the UI
  • NOTE: If you’re upgrading from 28.600, the watchdog issue above will prevent a normal upgrade. There are two options to workaround the watchdog bug to update to 28.601:
    • Uninstall the collector from its host, download collector 28.601 from the portal (you don’t need to delete or recreate the collector object in LogicMonitor) and install it on the host.
    • Open the collector debug window and run the !restart command to restart the collector. This will temporarily fix the environment (until the next automated collector credential rotation) and allow you to upgrade via the portal.
      • Restarting the collector via the drop-down UI menu won’t work for the workaround
      • Collector credential rotates every 24 hours

July 05, 2019

EA Collector – 28.600

Improvements:

  • Added RemoteSession protocol support for HTTP/S, VNC, and telnet.
  • Collector side configuration file service.conf is now website.conf

Fixes:

  • Fixed error that would cause system.collector property to show as false despite the resource being a collector
  • Fixed a bug introduced in EA 28.400 that would block collection reporting in some scenarios

June 21, 2019

EA Collector – 28.501

Fixes:

  • Fixed issue with Collector signing that could:
    • Cause false positives from anti-virus software
    • Block collection and reporting tasks

June 14, 2019

EA Collector – 28.500

Improvements:

  • Collector installer now uses Bash and interfaces with systemd. If you download 28.500 on v120 it will still use Perl.
  • !logsurf debug command will now show details for Test Script.
  • PIDs are now logged for troubleshooting external scripts.

Fixes:

  • Fixed bug that broke SNMP collection when two resources have the same IP address and different host names.
  • Avoid potential false No Data reported for Ping data collection when restarting Collector.
  • Fixed issue that would cause some NetFlow v9 data to be discarded in some circumstances.
  • Fixed issue that would cause Ping check to errantly return status 24 in edge cases.
  • Fixed a memory leak in the syslog collector.
  • Fixed bug that would cause JDBC collection to fail if special characters were in the URL.

May 23, 2019

EA Collector – 28.400

Improvements:

  • Added support for Test EventSource (SNMP trap, syslog, logfile) functionality
  • Collector now runs on Amazon’s Corretto JDK 11
    • Notes:
      • With this change, we’ve dropped support for 32-bit operating systems
      • At least initially, this will incur a roughly 10% increase in CPU and memory usage. We’re working to reduce this in future versions.
  • !logsurf debug command now provides additional log context from sbproxy.log (for WMI, Perfmon, and Ping tasks)
  • Improved PropertySource scheduling to avoid CPU spikes
  • The installer on Windows now confirms a successful install to avoid silent failure
  • Improved NetFlow performance by removing extraneous logging
  • Upgraded AWS SDK from 1.11.431 to 1.11.548 

Fixes:

  • Fixed !tplist “STATUS” field that would show OK despite there being an error

May 07, 2019

EA Collector – 28.300

Improvements:

  • Better monitoring of overall memory and CPU usage via a new Collector DataSource.
  • Reduce collector memory usage for Active Discovery history.
  • Linux collector will create a non-privileged logicmonitor user to run the collector when non-root is selected.
  • Support for running system’s snmpwalk and snmpget commands (useSystem=true)
  • Reduced SSE memory usage for Internal Web Checks
  • Improved WMI error handling logic to avoid gaps and return the real error code in more cases
  • Test Active Discovery for SNMP now returns diagnosis commands for both getNext and getBulk
  • Improve JMX data collection logic to avoid potential data gaps when invalid connections were errantly cached
  • Improved the uninstaller to completely remove the Collector in some scenarios where it was only partially uninstalled

Fixes:

  • Fixed potential memory leak with the ESX collector
  • Fixed an issue where the Windows Collector device name was shown incorrectly as “Unknown”
  • Fixed issue where syslog collector used excessive memory
  • Fixed the error that created a useless folder in the install directory


April 02, 2019

GD Collector – 28.002

Fixes:

  • Fixed batchscript collection caching behavior that would cause some instances with duplicate wildvalues to report No Data.
  • Fixed password exposure issue with Poll Now Diagnosis for WMI.

March 21, 2019

GD Collector – 28.001

Fixes:

  • Fixed issue where JDBC AD and Collection would fail if the domain name contains “-“.
  • Fixed memory leak issue with Groovy tasks.

February 27, 2019

GD Collector – 28.000

GD Collector 28.000 will be available February 27th, 2019. This version includes everything in GD 27.001GD 27.002GD 27.003GD 27.004GD 27.005, as well as EA 27.100, EA 27.200, EA 27.300EA 27.400, EA 27.500, EA 27.600, EA 27.700, EA 27.750, EA 27.751, EA 27.800, EA 27.850, EA 27.900.

In comparison to GD 27.001, highlights of this version include:

New Features:

  • Property Sources now support token replacement inside Powershell Scripts 
  • Added support for NTLMv2 authentication using wmi.authType
  • More insightful Poll Now error messages and diagnosis

Improvements:

  • Remote Sessions are now supported through a collector configured to use a proxy
  • Improved metrics for SSE and Collector performance monitoring
  • Syslog EventSources now correctly parse Cisco syslog messages lacking a host
  • Cleaned up collector logging
  • Fixed an issue where SSL validation prevented Groovy scripts from running successfully

For more detailed information on what’s included, see individual EA release notes (links above).

1 2 8 9 10