Welcome back to The Logstash Lines! In these weekly posts, we'll share the latest happenings in the world of Logstash and its ecosystem.
This week, David Pilato shows us how easy it is to use Logstash — instead of using rivers, which were recently deprecated — to index tweets into Elasticsearch:
New post: Indexing Twitter in #Elasticsearch with #Logstash http://t.co/MdgYtoIvNm #blog
— David Pilato (@dadoonet) June 2, 2015
Logstash Core and Plugins
- JDBC Input Plugin. Feedback Wanted! For those of you who use the JDBC river, which is now deprecated, we've got a solution in the works. Tal has been hard at work creating a replacement for it as a Logstash input plugin and he'd love your feedback on his proposal.
- Fixed an interesting deadlock issue in the pipeline reported by a user. The deadlock would occur when the filter worker tried to exclusively pop events off the internal queue while the periodic flush signal tried to push events onto the queue (but needed to wait for the queue to be empty).
- Added a configuration option to disable SSL certificate verification in the Elasticsearch output plugin. Although we do not recommend using this in production environments, users often find this useful while testing their deployment and for quick proofs of concept.
- Logstash 1.4.3 (bugfix release) was released last week.
- Expect Logstash 1.5.1 to be released this week.
That's this week in The Logstash Lines. Come back next week for more Logstash news!