Logstash 7.3.0 released | Elastic Blog
Releases

Logstash 7.3.0 released

We’re happy to announce the general availability of the Logstash 7.3.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 improvements

The pipeline-to-pipeline communication feature was introduced back in Logstash 6.3.0 as a new way to connect multiple pipelines within the same Logstash instance. Historically, monolithic pipeline configurations were commonly used to construct sophisticated processing logic for handling the data flow of multiple different data sources. Today, configurations can be effectively split out into separate, isolated pipelines that are stitched together with pipeline-to-pipeline communication. This helps both streamline performance and enhance processing modularity.

With Logstash 7.3.0, we've made a notable effort to spruce up this feature and have resolved all known bugs. Although still in beta, right now would be the perfect time to give it a spin. We look forward to any feedback you may have!


Consuming from JMS queues

Java Message Service (JMS) technologies are an important part of some of our users’ production environments. In Logstash 7.2.0, we overhauled the Logstash JMS input plugin, improving performance, security, and reliability. With the 7.3.0 release, we’re now bundling the JMS input plugin by default so its readily available as soon as you upgrade.

The JMS input plugin supports consuming data from any JMS technology into the Elastic Stack by embracing the bring-your-own-driver model, similar to the JDBC plugins. We encourage you to try it out with your own JMS deployments and let us know what you think! Curious what this looks like in action? Glad you asked — we have just the blog for you.


Feedback

Please download Logstash 7.3.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