When comparing Loggly vs ODE, 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 ODE is ranked 35th. 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 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
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 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.