Here’s the Deal

Loggly vs ODE

12 13

1 1

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 6th while ODE is ranked 35th. The most important reason people chose Loggly is:

[Unlike Airbrake](https://github.com/airbrake/airbrake-js/issues/82), you don't have to add try/catch blocks to automatically capture JavaScript errors.

Specs

Typeaggregation & monitoring

No specs yet!

Ranked in these QuestionsQuestion Ranking

Common Questions

What are the best log management, aggregation & monitoring tools?

Loggly

ODE

Pros

Pro
Automatically captures JavaScript errors

Unlike Airbrake, you don't have to add try/catch blocks to automatically capture JavaScript errors.

Pro
Hosted on a CDN already

Unlike Airbrake or LogEntries, you can download the library from GitHub and concatenate/minify it along with your other JS, or you can use it directly from Loggly's CDN.

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.