Some experimental conclusions about Sentry
December 20, 2018

Some experimental conclusions about Sentry

Anonymous | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Overall Satisfaction with Sentry

It is being used in our IT department and Quality department accordingly. We've integrated our product such that exception and logs can be collected by Sentry in more detailed and structural ways. Besides Sentry already can reach various transaction data via an agent which is installed on our production or test environments. Since then, Sentry can collect statistics continuously and robustly indeed. I use this tool to be notified of violations of the rules (system resources or load time based on concluded avg values, etc.), investigation of production or acceptance bugs, and also improvement opportunities in general.
  • 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 :)
  • This type of tool can prevent losing customers (ie money) if it is constructed properly
  • Also, you can predict the improvements or possible problems long before they happen
If you develop or sell a software product, you need to worry about its real production performance and previous stages. So, you can trace and observe, via software like Sentry, whether the product performed well always, or bury your hands in the sand until you are strangled by critical bugs.