v19.227-4

• Docker Stats source can now be configured to ingest metrics time series instead of JSON log messages. See Docker sources for details.
• Bug fix: Local and remote log file sources were not immediately detecting new or modified files in certain nested directory structures when a wildcard was used in the path expression.

v19.227-12

• Updated the Collector's cookie management policy to prepare for a receiver change.
• Bundled JRE version upgraded to 8u181.

v19.227-11

• Bug fix: When configuring Docker Sources without environment variables or labels null pointer exceptions were not handled appropriately.
• Bug fix: Remote File Sources were scanning from the current directory instead of the root directory when using leading wildcards in paths.

v19.216-38

• Bundled JRE version upgraded to 8u172.
• Bug fix: Misconfigurations in data forwarding could lead to high CPU usage.
• Bug fix: Extremely large Windows event log entries in an event channel could cause collection to stop for that channel.

v19.216-33: Merge pull request #64 from beyondbill/tmpl-escape

• Enhanced metadata allowing you to customize sourceCategory and sourceHost with environment variables, labels, and tags. Docker tags welcome, for more information see Collect Logs and Stats from Docker.
• Metrics support for Carbon 2.0 format has arrived with a new Source, Streaming Metrics. This will support Graphite format as well so our Graphite Source has been renamed. For more information, see Streaming Metrics Source.
• Data Forwarding is now more reliable for HTTP and Syslog destinations. Data is queued on disk when in-memory fills instead of causing your system to run out of memory. To configure your data forwarding queue limits see Forward Data from an Installed Collector.
• SystemD is now the default init system on Linux distributions that support SystemD.
• Simplified installation for the Linux binary package as a result of an updated Tanuki wrapper. For more information, see Install a Collector on Linux.

More details here

v19.209-41

• Changes to upgrade codepaths in preparation for upcoming release.
• Bug Fix: Collector unable to start after an upgrade when using a custom installation path on Windows 32-bit.

v19.209-37

• Bundled JRE version upgraded to 8u162.

v19.209-26

https://help.sumologic.com/Release-Notes/Collector-Release-Notes

• Bug fix: Docker stats source failed to start and collect stats.
• Bug fix: Added a socket timeout when connecting to HTTP proxy servers to prevent the collector from going offline.

v19.209-23

https://help.sumologic.com/Release-Notes/Collector-Release-Notes

• The Sumo collector is updated to include the latest Java 8 JRE from Oracle, version 8u152. Collectors bundled with a JRE will automatically be upgraded to JRE version 8u152 upon installation.
• Added support for preserving Access Key in the user.properties file after the collector registers with the Sumo service. The new parameter for the command line installer is -VskipAccessKeyRemoval=true. The corresponding property in user.properties is skipAccessKeyRemoval=true.
• Added support for specifying the sources for a collector in a directory of JSON source files when registering a collector with cloud-based source configuration. Previously, you could only specify a file with the sources property in the user.properties file. Now you can specify a folder of JSON files with the sources property.
• Bug Fix - Docker stats sources unexpectedly stopped.
• Bug Fix - Implemented targeted optimizations to reduce CPU usage and disk I/O for certain local file sources.
• Bug fix - In some cases, the HTTP sender stopped sending data after loss of connectivity.

v19.209-8

• Bug Fix - Host Metrics sources don't correctly handle source renaming, leading to double-ingest
• Bug Fix - Docker stats sources don't honor mask in processing rules
• Bug Fix - Docker stats sources may fail with “Error getting container info” message in log

https://help.sumologic.com/Release-Notes/Collector-Release-Notes