From eb80b81bc5290d19a4b9f89d2a7e46af32524751 Mon Sep 17 00:00:00 2001 From: Holger Reinhardt Date: Wed, 3 Feb 2016 16:54:54 +0100 Subject: [PATCH] final tweak --- _posts/2016-01-11-log-aggregation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2016-01-11-log-aggregation.md b/_posts/2016-01-11-log-aggregation.md index f16116f..fd759ec 100644 --- a/_posts/2016-01-11-log-aggregation.md +++ b/_posts/2016-01-11-log-aggregation.md @@ -29,7 +29,7 @@ Elasticsearch becomes the nexus for gathering and storing the log data and it is Another very good data collection solution on the market is Fluentd, and it also supports Elasticsearch (amongst others) as the destination for it’s gathered data. So using the same data repository and frontend solutions, this becomes the EFK stack and if you do a bit of searching you will discover many people have chosen to substitute Elastic's logstash with FluentD and we will talk about why that is in a minute. {:.center} -![Log aggregation Efk]({{ site.url }}/images/logaggregation-efk.png){:style="margin:auto; width:50%"} +![Log aggregation Efk]({{ site.url }}/images/logaggregation-efk.png){:style="margin:auto; width:40%"} # Logstash vs FluentD Both of them are very capable, have [hundreds](https://www.elastic.co/guide/en/logstash/current/input-plugins.html) and [hundreds](http://www.fluentd.org/plugins) of plugins available and are being maintained actively by corporation backed support.