Collector Release Notes Timeline

GD Collector – 27.004

Fixes and improvements:

• SSE will be automatically disabled on collectors that can’t support it due to insufficient RAM and other edge cases.
• Improved memory efficiency for WMI, Perfmon, and Ping collection.
• Improved SSE memory usage when consuming the hosts feed, particularly for collectors handling large numbers of instances.
• Various stability improvements.
• Reverted JSch library to 0.1.53 from 0.1.54 to fix a compatibility issue with some Cisco devices.
• Fixed issue where sbproxy would be errantly terminated.

GD Collector – 27.003

Fixes and improvements:

• The SSE engine now supports custom lib folders, including relevant paths, for 3rd party jars.
• Added an option to execute parallel perfmon metric collection for situations where some parent metrics might be invalid.
• Added additional status monitoring of the Collector Reporter to identify situations where the Collector may be reporting data, but not gathering fully.
• Fixed a bug where the Collector was being repeatedly restarted by improving the logic that Watchdog uses to restart the collector agent.
• Fixed a bug in SNMP collection when gathering metrics individually which resulted in “ConcurrentModificationException” errors.
• Fixed a bug where certain Groovy Scripts would not work and display this error “Cannot schedule task for execution” after disabling the Standalone Scripting Engine.
• Fixed a bug where “reporter.persistent.queue.consume.rate” config setting was not being used.
• Fixed a bug where very large host entries would cause an OutOfMemory exception. The script will be scheduled for later execution or SSE will be disabled until next restart when the process does not register within a configured initiation time.
• Fixed a resource leak in Standalone Scripting Engine and added increased protection for OutOfMemory exceptions and SSE spawning too many processes.
• Increased security to prevent DLL hijacking in sbwinproxy.

GD Collector – 27.002

Fixes and improvements:

• Fixed an issue where SSL Certs validation was preventing certain Groovy Scripts from successfully running.
• Fixed an issue with the Watchdog process frequently restarting SBProxy process.
• Fixed an issue where upgrading from 26.XXX to 27.XXX resulted in more variability in Data Collection Task counts. The timeout value for collector.max.init.delay.in.seconds is now defaulted to 600.
• Fixed an issue when perfmon initialization against a slow endpoint may cause an restart of the sbroxy service.

GD Collector – 27.001

Fixes and improvements:

• Fixed an issue where JDBC data collection and making TLS connections.
• SBWinProxy was restarting randomly and impacting the ability to monitor Ping datasources.
• Improved the default Memory Allocation around the scripting environment.
• When proxy.enable=true in agent.conf, the collector will check the proxy certificate for validity. The collector will not connect to Santaba if the certificate fails the validity check.

GD Collector – 27.000

GD Collector 27.000 will be available June 12, 2018. This version includes everything in GD 26.001, as well as EA 26.100, EA 26.200, EA 26.201, EA 26.300, EA 26.400, EA 26.500, EA 26.600 and 26.601

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

New Features:

• Property Sources now support Powershell Scripts
• Removed Support for Windows 2003
• Windows Collector installer and files are now signed
• Support for Event Source Test Now functionality (similar to Poll Now on datasources)

Improvements:

• Added support for 3-DES for SNMP v3
• Service Checks now support the ability to identify SSL errors and halt on them as separate actions.  Therefore the check can identify the SSL error, but continue to confirm the rest of the service functionality.
• Groovy Scripting will now support PUT and DELETE methods as part of an updated HTTP java class.

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

GD Collector – 26.001

GD 26.001 will be released January 23rd, 2018 to replace GD 26.000, which was released early January.

GD 26.001 fixes an issue identified in GD 26.000 that could affect LogicMonitor performance. If you are running 26.000, please update to this new 26.001 version.

GD Collector – 25.001

GD 25.001 will be released October 25th, 2017 to replace GD 25.000, which was released early September. We have subsequently identified an issue in GD 25.000 that could cause problems with PowerShell script execution under certain conditions. With GD 25.000, we improved the ability of the Collector to trap PowerShell exceptions, and it is possible this would terminate PowerShell script execution for otherwise harmless errors. We have corrected and thoroughly tested this in GD 25.001. 

If you’ve upgraded to 25.000 and have not experienced these issues, you are welcome to continue with GD 25.000. However, if you have noticed any trouble with PowerShell collection – or just want to be cautious – please upgrade to version 25.001 at your convenience.

EA Collector – 22.253

EA Collector 22.253 will be released December 23, 2016, and includes the following:

Improvements:

• We’re now setting a discover.workers option for new Collectors (in the Collector’s agent.conf file).  This value is based on the selected Collector size, and changes the threadpool resources allocated for Active Discovery.
• XML DataSource post processing wasn’t working for DOCTYPE XML data.  This was due to a previous security improvement.  We’ve improved how the security improvement was implemented to allow XML DOCTYPE DataSource post processing.
• Log File EventSource alerts weren’t always showing the complete log file path if glob was used in the EventSource definition.  We’ve made improvements such that the full log file path is always displayed in the alert message. 

Bug Fixes:

• Internal Service checks with the character $ in the POST body (e.g. in a password) were failing for Collector versions > 22.180.  This was due to the $ character not being escaped correctly by the Collector, and has been corrected with version 22.253.
• Testing Windows Collector connections in the Java configuration dialog wasn’t always working.  This was due to the Collector’s credential not being decrypted correctly for the connection test, and has been corrected.
• Collectors handling very large volumes of Netflow v9 traffic were sometimes having issues reporting Netflow data. 
• In EA 22.227 we added logic to verify that the Collector’s sbshutdown process was only shutting down the Collector’s “java.exe” process.  There was one remaining case where this remained an issue, and we’ve corrected this issue with EA 22.253.
• With EA 22.180 we disabled the gssapi-with-mic and keyboard-interactive user authentication methods for SSH via the Groovy Expect-like API.  However, there were a few rare DataSources that utilized the keyboard-interactive authentication method.  In EA 22.253 we’ve added keyboard-interactive authentication back in.
• Disabling Syslog EventSource collection didn’t always prevent the Collector from listening on port 514.  This has been corrected.
• The memory check that occurs during Collector installation wasn’t respecting silent Collector installations.  This has been corrected.
• Windows Event Logs with an empty attribute field weren’t being correctly reported by the Collector, and therefore weren’t showing up in LogicMonitor.  We’v added logic that ignores empty fields to correct this issue. 
• The files in the Collector directory only need 755 permissions for the Collector to run.  When the Collector is installed these files are created with the right permissions, but the Collector upgrade process was changing permissions to 777.  This has been corrected. 

MGD Collector 22.005

At the beginning of this month we announced 22.004 as our new minimum Collector version.  We’ve since identified a somewhat uncommon scenario that 22.004 falls short in, and are releasing a new MGD 22.005.  With MGD 22.004, Collectors that are handling 3000+ Groovy script tasks, where the Groovy scripts reference ##WILDVALUE## for dynamic multi-instance data collection, may restart too frequently.  The restarting is due to a JDK 8 Metaspace OOM (out of memory) exception that occurs because of the memory needed to handle the ##WILDVALUE## syntax in Groovy scripts.  With MGD 22.005 we’ve removed the Metaspace memory limit and improved how the ##WILDVALUE## syntax is handled in Groovy scripts, decreasing the amount of memory needed.  We’ve tested this extensively, and believe it does solve the issue at hand. 

If you’ve already upgraded to 22.004 and haven’t noticed any issues, your Collectors may not be impacted by the current issue.  You are welcome to continue with version 22.004, and at this point in time you will not be forced to upgrade to 22.005.  That being said, we do believe that version 22.005 is better than version 22.004.

MGD 22.005 will be released October 19th, 2016, and we will start scheduling automatic upgrades for all Collectors below version 22.004 after November 18th.

Note: Websites that have certificates relying on SHA256withDSA as the signature algorithm may display SSL errors for Collector versions 20.074 or higher.  This is due to a known JDK 8 issue.  We plan to release a new EA Collector with an upgraded JRE as soon as possible.