Papertrail vs ODE

To set Papertrail up, use NXLog, or simply direct logs to a URL provided by Papertrail. No proprietary agent.

The default view is mostly taken up by log events with a small row at the bottom for entering a search query, setting date range, accessing saved searches and enabling or disabling real-time logging.

By default log events and searches in Papertrail are updated in real-time.

Logs can be colorized by installing Stylish, a browser extension for Chrome and Firefox that overrides CSS stylesheets, and writing a custom stylesheet.

Papertrail's log entries have various attributes that can be used to change css properties for specific programs or systems, or based on message contents.

Logs can also be colorized within the actual logs by adding ANSI escape codes (will override user-specific colorization).

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.

You can add any parser you want to ODE.