When comparing Fluentd vs Splunk, 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 Splunk is ranked 11th. The most important reason people chose Fluentd is:
Gives structure to unstructured logs.
Specs
Ranked in these QuestionsQuestion 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 Easy to use, powerful search
It's human readable, intuitive, fast and with auto-complete to boot. And if you need more advanced functionality out of your queries, 120+ page search manual will give you an insight in how much is actually possible.
Pro Widely used
De facto standard for log aggregation, monitoring, analysis and reporting.
Pro Scales effortlessly
It is built for enterprise use, meaning it scales easily.
Pro Real-time graphs
You can create visualizations that update in real time.
Pro Cross-platform
OS X, Linux & Windows are supported. You can also access Splunk from iOS and Android devices.
Pro Free version
With restrictions on log size and devices a free version is available.
Pro Alerts
Splunk can turn searches into alerts.
Pro Understands data in any format or language
Pro Extendable via a large selection of apps
Additional functionality can be added with over 500 apps.
Cons
Con Difficult to setup
Requires a significant time investment to get up and running.
Con Expensive
Splunk is pretty expensive compared to other solutions.
Con Antiquated
The interface and service are very antiquated
Con Seriously SLOW ingest
Their docs and sales say it will ingest up to 20k EPS, but reality is more like 1k eps per server.