Product release

Logstash 7.4.0 released

By
Alvin Chen

We’re happy to announce the general availability of the Logstash 7.4.0 release. This is the latest stable release and is now available for download! Please refer to the release notes for the complete list of bug fixes and features.

Pipeline-to-pipeline communication GA

The pipeline-to-pipeline communication feature is now officially GA with the Logstash 7.4.0 release, enabling a production ready approach for connecting multiple pipelines within the same Logstash instance. This provides our users the ability to leverage more pipeline logic isolation and modularity, ultimately leading to better processing performance while retaining at-least-once delivery semantics across the entire chain of delivery.

The power of chaining pipelines unlocks a plethora of different use cases in practice. Whether you want to separate processing logic for multiple data types coming through a single input or guarantee stronger delivery when using multiple outputs, pipeline-to-pipeline communication allows sophisticated processing to be done more efficiently and in an easier to manage fashion. Check out a few different architectural patterns we’ve outlined as inspiration; we’re excited to see the myriad of ways you may take advantage of this feature in your own deployments!

NetFlow module deprecation

The Logstash NetFlow module has been deprecated in Logstash 7.4.0 and we plan to remove it completely in a future major release. For users interested in NetFlow data analysis, we recommend checking out the Filebeat NetFlow module. It has functional parity with the Logstash module equivalent while complying with the Elastic Common Schema (ECS) for easy usage with the Elastic SIEM application and more seamless correlation with other data sources that reside together in your Elastic Stack deployment.

Try it out yourself!

Please download Logstash 7.4.0, try it out, and let us know what you think on Twitter (@elastic) or in our forums. You can report any bugs or feature requests on the Logstash Github issues page or within the respective plugin repositories.