When comparing Sentry vs Sumo Logic, the Slant community recommends Sentry for most people. In the question“What are the best log management, aggregation & monitoring tools?” Sentry is ranked 4th while Sumo Logic is ranked 12th. The most important reason people chose Sentry is:
It's what Sentry calls [Rollups](https://docs.sentry.io/learn/rollups/]. All individual issues rolled-up can still be drilled down. Also two issues can be **merged** manually.
Ranked in these QuestionsQuestion Ranking
Pro Consolidates similar errors and makes resolution easy
It's what Sentry calls [Rollups](https://docs.sentry.io/learn/rollups/]. All individual issues rolled-up can still be drilled down. Also two issues can be merged manually.
Pro Email/Slack/GitHub/Hipchat integration
Newly discovered issues (i.e. one that isn't rolled-up under and existing one) can generate an instant notification via many means.
Pro Has an official Docker image
Sentry has an official Docker image which means it's likely going to be well reviewed and maintained for a while and it makes it easy to set up.
Pro Completely open source, with a hosted version available
Sentry is a completely open source tool. It's free to use if you want to run it on your own. If you want to avoid the overhead of running and maintaining another server, it also has a hosted version available at www.getsentry.com
Pro Source maps support
Has support for source maps.
Pro Can create projects and teams
A single Sentry server can be used for various teams/products.
Sumo logic is entirely cloud based and very scalable.
Pro Flexible licensing model
Licensing cost is primarily determined by daily ingest of logs, however this is averaged out over 30 days instead of locking a user out of their own data after an arbitrary number of license breaches.
Pro Truly multi-tenant
Sumo Logic is truly multi-tenant, a single instance running on the server can serve multiple groups of users.
Pro A large set of supporting Apps
Allows customers to quickly setup and start getting actionable insights from their infrastructure by using Apps that integrate with various different platforms out of the box.
Con Not really a logging solution
Sentry collects exceptions, it's not a solution for log aggregation.
Con Can't filter by browser versions
Sentry only filters by browser names and not by browser versions (for example: Firefox, instead of Firefox 27, Firefox 28 etc...)
Con No free cloud hosting
Unfortunately there is no free plan for cloud hosted solution. Only self-hosted solutions are free to use.
Con Useless need for collectors
You have to install a plugin on each host to collect logs, the collector is 89MBs and is written in Java. there's no reason to install a Java tool to send syslog data when Linux already does that natively. The memory footprint for Java-based apps is way too high and, in this case, completely unnecessary.
Con Does not support structured data
They don't support RFC5424 standard events
Con Install is very painful
Con Search is very difficult
Here's an example:
_sourceCategory=*windows* _sourceName=Security (4771 OR 4768 OR 4776 OR 4625) | parse regex "EventIdentifier = (?<event_id>\d+?);" | parse regex "ComputerName = \"(?<hostname>.+?)\"" | parse regex "(?:Result|Failure|Error) Code:.+?(?<result_code>0x[A-Fa-f\d]+)\b" nodrop | where result_code !="0x0" AND event_id in ("4771", "4768", "4776","4625") | count by hostname
Con Indexing and search are very slow
Sending around 45000 events to it may take more than 3 minutes to show up in the interface.
Once they show up, a search may take up to 32 seconds to return results. On only 45000 events, the search should return in milliseconds.
Con Difficult / Confusing Interface
The service and interface are very confusing.
Con There can be issues with smaller vendors
There may be some issues when using devices and services for smaller vendors which are not officially supported by Sumo Logic.