When comparing Flume vs ODE, the Slant community recommends Flume for most people. In the question“What are the best log management, aggregation & monitoring tools?” Flume is ranked 14th while ODE is ranked 35th.
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 Scales easily
ODE instances are independent of each other, so they don't have to worry about a peer being added/removed. This allows the cluster to grow without any performance hit on the log aggregation. There is no redundancy built-in, but you can always use the forwarder to duplicate data. There is no sharding configuration or any other penalty that comes up with scaling a cluster. The clustering configuration is also very easy where you just list out peers for one of the node in order for it to run a search query on the whole cluster and merge the results. Scales better than any other open source log management tool out there.
Pro Add new parsers as you like
You can add any parser you want to ODE.
Pro Highly customizable
Pro Easy to use
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 Still in beta
Opallios ODE seems to be still in beta, as such there may be issues or missing features which are not yet implemented.