Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Loggly vs Fluentd, the Slant community recommends Fluentd for most people. In the question“What are the best log management, aggregation & monitoring tools?” Fluentd is ranked 4th while Loggly is ranked 6th. The most important reason people chose Fluentd is:
Gives structure to unstructured logs.
Specs
Question Ranking
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 Logs everything in JSON
Gives structure to unstructured logs.
Pro Logs stored to FS buffer while network is down
Logs aren't lost due to network issues.
Pro In-stream processing
With a list of 150+ plugins, Fluentd can perform all kinds of in-stream data processing tasks.
Pro Huge plugin ecosystem
Fluentd has a plugin ecosystem that has resulted in developers creating over 150 plugins for the service.
Pro Prioritizes simplicity and robustness
For example, inputs and outputs have built-in support for buffering, load-balancing, timeouts and retries so to be able to deliver data reliably.
Pro Free and open source
Licensed under Apache 2.0.
Pro Routing based on tags
Pro Exponential retry wait
Pro Copy to multiple storages
Pro Based on CRuby
Cons
Con Expensive
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 JavaScript tracker has removed tag support
Con Difficult to setup
Requires a significant time investment to get up and running.
