<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Logstash on Giedrius Statkevičius</title><link>https://giedrius.blog/categories/logstash/</link><description>Recent content in Logstash on Giedrius Statkevičius</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 13 Aug 2019 18:26:43 +0000</lastBuildDate><atom:link href="https://giedrius.blog/categories/logstash/feed.xml" rel="self" type="application/rss+xml"/><item><title>ABCs of Logstash capacity planning</title><link>https://giedrius.blog/2019/08/13/abcs-of-logstash-capacity-planning/</link><pubDate>Tue, 13 Aug 2019 18:26:43 +0000</pubDate><guid isPermaLink="false">https://giedrius.blog/?p=574</guid><description>&lt;p&gt;Recently I had to do some capacity planning of this software that is relatively popular and it stands for the L in the ELK (Elasticsearch, Logstash, Kibana) stack so I thought that I should share what I have learned. While researching, I have found an appalling lack of information regarding this matter so I hope that this article will at least a bit help fill this void on the Internet.&lt;/p&gt;</description></item></channel></rss>