Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Fluentd vs Graylog2, the Slant community recommends Fluentd for most people. In the question“What are the best log management, aggregation & monitoring tools?” Fluentd is ranked 4th while Graylog2 is ranked 7th. The most important reason people chose Fluentd is:
Gives structure to unstructured logs.
Specs
Question Ranking
Pros
Pro Logs everything in JSON
Gives structure to unstructured logs.
Pro Logs stored to FS buffer while network is down
Logs aren't lost due to network issues.
Pro In-stream processing
With a list of 150+ plugins, Fluentd can perform all kinds of in-stream data processing tasks.
Pro Huge plugin ecosystem
Fluentd has a plugin ecosystem that has resulted in developers creating over 150 plugins for the service.
Pro Prioritizes simplicity and robustness
For example, inputs and outputs have built-in support for buffering, load-balancing, timeouts and retries so to be able to deliver data reliably.
Pro Free and open source
Licensed under Apache 2.0.
Pro Routing based on tags
Pro Exponential retry wait
Pro Copy to multiple storages
Pro Based on CRuby
Pro Free and open source
Graylog2 is licensed under GNU GPL v3.
Pro Easy setup
Graylog2 can be quickly installed on any Linux machine running Java 7 via an executable that allows installing and configuring remote dependencies and graylog2 itself via a web interface.
Pro Real-time
Information and statistics displayed update in real time.
Pro Great interface
Easy to overview, intuitive and full of explainers.
Pro Little maintenance
Pro Streams allow identifying events in real-time and perform actions
Stream allow filtering events in real time and perform action such as issue alerts or forward messages.
Pro Server-side functionality can be extended via plug-ins
Pro Works well with just about any type of logging
Cons
Con Difficult to setup
Requires a significant time investment to get up and running.
Con Limited logging protocols support
Graylog2 only has support for syslog and GELF.
Con Self hosted. Difficult to maintain.
Maintenance is very difficult because of the high volume nature of logs.
Con Slow
Takes multiple servers even for smaller deployments
Con Interface is hard to use
The interface is hard to use, loaded with data, and difficult to understand.
