<story><title>Logstash joins Elasticsearch</title><url>http://www.elasticsearch.com/blog/welcome-jordan-logstash/</url></story><parent_chain></parent_chain><comment><author>clarkdave</author><text>Logstash, Elasticsearch and Kibana are just fantastic. After being unsatisfied with a whole bunch of Logging As A Service providers (I tried loggly.com, logentries.com and splunkstorm.com) I spent an afternoon setting up Logstash and co and couldn&amp;#x27;t be happier.&lt;p&gt;There&amp;#x27;s a neat demo of Kibana here: &lt;a href=&quot;http://demo.kibana.org/#/dashboard/elasticsearch/Logstash%20Search&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;demo.kibana.org&amp;#x2F;#&amp;#x2F;dashboard&amp;#x2F;elasticsearch&amp;#x2F;Logstash%20...&lt;/a&gt;&lt;p&gt;The only thing that isn&amp;#x27;t fully baked in with this stack is alerts (e.g. sending an email if a certain error log message comes in), but you can do that using Logstash filters and outputs, although there&amp;#x27;s no pretty UI.&lt;p&gt;There are some excellent Chef cookbooks for setting up Logstash and friends too:&lt;p&gt;- Logstash: &lt;a href=&quot;https://github.com/lusis/chef-logstash&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;lusis&amp;#x2F;chef-logstash&lt;/a&gt;&lt;p&gt;- Elasticsearch: &lt;a href=&quot;https://github.com/elasticsearch/cookbook-elasticsearch&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;elasticsearch&amp;#x2F;cookbook-elasticsearch&lt;/a&gt;&lt;p&gt;- Kibana: &lt;a href=&quot;https://github.com/lusis/chef-kibana&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;lusis&amp;#x2F;chef-kibana&lt;/a&gt;</text></comment>
<story><title>Logstash joins Elasticsearch</title><url>http://www.elasticsearch.com/blog/welcome-jordan-logstash/</url></story><parent_chain></parent_chain><comment><author>benmmurphy</author><text>logstash + elasticsearch are pretty amazing. however, if you are generating a high rate of log entries you may want to consider using mozilla hekad instead (&lt;a href=&quot;http://hekad.readthedocs.org/en/latest/&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;hekad.readthedocs.org&amp;#x2F;en&amp;#x2F;latest&amp;#x2F;&lt;/a&gt;). on our servers logstash was running around 20% CPU during quite periods while hekad was running around 1-2% CPU. while during busy periods i think logstash was going up to 100% CPU while hekad was sitting around 20-30% CPU.&lt;p&gt;hekad is written in go which compiles down to native code while logstash is written in jruby which is not the most performant runtime.</text></comment>