When comparing Loggly vs Splunk, 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 Splunk is ranked 11th. 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
Ranked in these QuestionsQuestion 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 Easy to use, powerful search
It's human readable, intuitive, fast and with auto-complete to boot. And if you need more advanced functionality out of your queries, 120+ page search manual will give you an insight in how much is actually possible.
Pro Widely used
De facto standard for log aggregation, monitoring, analysis and reporting.
Pro Scales effortlessly
It is built for enterprise use, meaning it scales easily.
Pro Real-time graphs
You can create visualizations that update in real time.
Pro Cross-platform
OS X, Linux & Windows are supported. You can also access Splunk from iOS and Android devices.
Pro Free version
With restrictions on log size and devices a free version is available.
Pro Alerts
Splunk can turn searches into alerts.
Pro Understands data in any format or language
Pro Extendable via a large selection of apps
Additional functionality can be added with over 500 apps.
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 Expensive
Splunk is pretty expensive compared to other solutions.
Con Antiquated
The interface and service are very antiquated
Con Seriously SLOW ingest
Their docs and sales say it will ingest up to 20k EPS, but reality is more like 1k eps per server.