When comparing Loggly vs Flume, the Slant community recommends Loggly for most people. In the question“What are the best log management, aggregation & monitoring tools?” Loggly is ranked 8th while Flume is ranked 14th. The most important reason people chose Loggly is:
Ranked in these QuestionsQuestion Ranking
Pro Supports raw text, syslogs, and JSON
Raw text, syslogs, and JSON can be fed to Loggly.
Pro Easy to set up
You only have to set up a HTTP JSON input and there are community examples to guide you.
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.
Loggly QUICKLY overflows the 200mb daily free allowance.
Con Difficult to setup
Setup is not easy, the whole process is disjointed, with open source libraries that regularly change and out of date installation instructions.
Con The UI is confusing
The UI is very difficult to use, but it does offer a lot of features.
Con Timestamps are in UTC in the UI, and can't be converted
Loggly shows all timestamps in UTC, and the bookmarklet that's supposed to convert them to local time doesn't work.
Con Hard to manage
Since Flume cannot do multiplex connections, it's extremely hard to manage. It's essentially one socket per log type.