Logstash 7.8.1 Release Notes
editLogstash 7.8.1 Release Notes
editPerformance improvements and notable issues fixed
editFixed performance regression during pipeline compilation
editA performance regression was introduced in 7.7.0, as described in the 7.8.0 release notes. The issue was caused by an enhancement - #11078 - that included the plugin ids in log entries produced by Logstash pipelines. The implementation of this feature has been fixed and no longer causes the performance issue. You can find more about the solution here #12038.
Multiple fixes to pipeline shutdown and reloading
edit7.8.1 brings many fixes that improve the stability of the pipeline lifecycle. In previous releases, enabling monitoring could result in Logstash crashes if pipelines from concurrent pipeline reloads (fixed in #12034). Also, pipelines failing to start correctly could prevent the Persistent Queue from being used afterwards (fixed in #12023). Finally, a JRuby issue concerning threads and the Ruby/Java implementation boundary could cause crashes during pipeline reloads, and this has been fixed in #11900.
Changes in the dependencies of Beats/TCP/HTTP Input Plugins
editTo avoid breaking changes and retain control on the set of ciphers exposed in these plugins, underlying dependencies (tcnative and boringssl) have been dropped in favor of using JVM supplied ciphers instead.
Overall there should be no impact but this may result in fewer ciphers being available if the JCE unlimited strength jurisdiction policy is not installed.
NOTE: This policy is installed by default on versions of the JDK from u161 onwards.
You can find more information in the release notes of the respective plugins.
Plugins
editXml Filter - 4.1.1
- Fix: exceptions thrown while handling events no longer crash the pipeline #73
Beats Input - 6.0.11
-
Updated jackson databind and Netty dependencies. Additionally, this release removes the dependency on
tcnativeandboringssl, using JVM supplied ciphers instead. This may result in fewer ciphers being available if the JCE unlimited strength jurisdiction policy is not installed. (This policy is installed by default on versions of the JDK from u161 onwards.) #393 - Added error handling to detect if ssl certificate or key files can’t be read #394
Elasticsearch Input - 4.6.2
Http Input - 3.3.5
-
Updated jackson databind and Netty dependencies. Additionally, this release removes the dependency on
tcnativeandboringssl, using JVM supplied ciphers instead. This may result in fewer ciphers being available if the JCE unlimited strength jurisdiction policy is not installed. (This policy is installed by default on versions of the JDK from u161 onwards.) #126
Syslog Input - 3.4.3
- [DOC] Added expanded descriptions and requirements for facility_labels and severity_labels. #52
Tcp Input - 6.0.6
-
Updated Netty dependencies. Additionally, this release removes the dependency on
tcnativeandboringssl, using JVM supplied ciphers instead. This may result in fewer ciphers being available if the JCE unlimited strength jurisdiction policy is not installed. (This policy is installed by default on versions of the JDK from u161 onwards.) #157
Jdbc Integration - 5.0.5
- Fixed user sequel_opts not being passed down properly #37
- Refactored jdbc_streaming to share driver loading, so the fixes from the jdbc plugin also effect jdbc_streaming
- Fixed issue where JDBC Drivers that don’t correctly register with Java’s DriverManager fail to load (such as Sybase) #34
- Fixed issue where a lost connection to the database can cause errors when using prepared statements with the scheduler #25
- Fixed potential resource leak by ensuring scheduler is shutdown when a pipeline encounter an error during the running #28
S3 Output - 4.3.2
- [DOC]Added note that only AWS S3 is supported. No other S3 compatible storage solutions are supported. #223