When comparing Flume vs Timber, the Slant community recommends Flume for most people. In the question“What are the best log aggregation & monitoring tools?” Flume is ranked 14th while Timber is ranked 36th.
Ranked in these QuestionsQuestion Ranking
Pro Flume is transactional (no lost when duplicating streams), and can be backuped by Kafka
Pro Hadoop integration
Flume was created to efficiently move log data to Apache Hadoop's HDFS.
Pro Free and open source
Licensed under Apache 2.0.
Pro Beautiful, modern, easy interface
The Timber interface stands out in the space:
- It's beautiful, easy, and modern.
- It's fast. It uses advanced front-end technologies to maximize performance and usability (react, redux, etc).
Pro Great search
Timber offers a really great simple search, with a support for advanced features like: term negation, condition grouping (parenthesis), regex, field searches and conditions, etc.
Pro Six month searchable retention
The retention Timber offers is exceptionally longer. The default is generally 2 - 4 weeks, Timber offers 6 months.
Pro Easy installation
Timber can be installed in < 1 min and usually with a single command. It asks your for your application details and provides 1 set of simple instructions.
Pro Automatic context & structured data
Timber provides native libraries that automatically attach metadata to your logs. They've designed a schema that defines events and context, which normalizes the data and makes querying, alerting, and graphing simple and reliable.
Pro Real-time graphing
Because Timber fully embraces structured data, graphing is simple, real time, and fast. They provide a number of aggregates you can graph on.
Pro Real-time alerts with thresholds
The alerts are real-time and the approach is thoughtful. Instead of blasting you with alerts every time it's triggered, they change the state of the alert once, notify you once, and then notify you again when the alert is no longer an issue.
Pro Simple pricing and plans. No feature matrices.
Besides the free plan, Timber doesn't impose limits on the number of users, alerts, etc. It's entirely based on the amount of data allowed for the plan. It's refreshingly straightforward.
Pro No rate limiting
Beyond the space your plan is allowed to use, there is no rate limiting.
Pro Excellent documentation
Timber's docs are detailed and thoughtful, both for the service as well as the libraries they offer.
Pro SQL query your logs (w/ join support)
Timber allows you to SQL query your logs just like you would a traditional database. The JOIN support is very powerful.
Pro Logs show up quickly
Logs show up < 3 seconds of when they are generated
Con Hard to manage
Since Flume cannot do multiplex connections, it's extremely hard to manage. It's essentially one socket per log type.
Con Not really a centralized log management tool
It only takes in events from specified "apps", not all unstructured data. And, if you select "other" (apps), it just says:
Bummer! We don't support apps of this type yet.