Sentry

It collects very detailed information on problems that happen to our users while using the platform

It supplies very good tools in order to aggregate the collected data and analyze it

It integrates with Slack, making it easier to "monitor it in real time"

The UI is overwhelming and it takes time to "digest it"

It would have been nice to have the ability to "group together" minor releases into one that represents a bigger release

Application Monitoring

Performance Monitoring

Page Speed and Core Web Vitals Monitoring

Source Code Integration (Regression Monitoring)

More useful stack track

Better grouping of related issues instead of them coming in as separate issues

More insight into each issue in terms of which ones actually impacted the user

Great user experience

Real time alerting

Wide range of supported SDK languages

Alert Configuration. Would be really helpful to have multiple logical groupings within the "If" section of a single configurable alert.

Alert Copying. Being able to copy an alert from one project to another would be super beneficial.

Alert Tags. Better UI around how we select which tags are getting sent with each alert instead of a tiny text box.

Easy install.

Issues alerting.

An easy to use interface.

It doesn’t slow down our site.

It needs easier to find GTM Install Instructions.

Great at giving us a proactive heads up when there may be a serious issue in production by notifying us when a certain exception happens many times.

Excellent variety of supported platforms: .NET, Java, and many more.

Tracks exceptions across multiple releases, so you can identify when an exception first started happening.

Sentry rolls up exceptions that it feels are similar, but the logic to determine that similarity could be improved. It doesn't always merge exceptions that are similar.

The UI could be improved around projects; it would be nice to be able to group them by an environment.

Support for .NET could be improved, it required us to roll our own library to log to Sentry.

Cut out for the investigations of problems (with a log tool also)

Finding improvements is easier

Detecting bottlenecks may be possible in advance

Any throughput can be observed

May need you to develop and put the code into your codebase which is specialized for Sentry (in case of you want to get more information from Sentry)

It is complex to use (and sometimes slow, especially when digging into some data that depends on historical stats) although it is a very handy and flexible tool

Management is getting worried about the pricing :)

Sentry doesn't just provide a list of errors and exceptions, but instead gives us a full stack trace to work from

Internally, Sentry handles a lot of code versioning checks so we can see where errors originated from, and if deployed fixes are in fact working

Sentry interfaces with existing reporting tools so we can respond to production exceptions in minutes, instead of when we find out about them in viewing logs

Very much a one-off tool; Sentry would be a lot nicer to use if it built out additional monitoring tools so we could run the entirely of our logging and reporting through their software

Some of their documentation, particularly for the open source projects that drive error collection, can be lacking or inadequately communicated

Great web interface. Lots of data available in a really clean format, with filtering options and more.

Per-user exception tracking. User is complaining about something being broken? Look up their account ID in Sentry and you can see if they've run into any exceptions (with device information included, of course).

Source map uploading. Took a little while to figure this out but now we have our deploy script upload sourcemaps to Sentry on each deployment, meaning we get to see stack traces that aren't obfuscated!

Very generous free tier – 10,000 events per month. We're nowhere near that yet.

Rollbar has more integrations with other services such as Help Scout. Would be nice if Sentry had as many.

Can't search for users by username, even though I'm supplying one with the client SDK. I have to find their database ID first.