Before we deep dive into the topic let’s focus on why we need this tool and why we need this feature in our toolbox. In the world of errors and bugs, we will find many errors to debug and keep our system stable. So many applications need monitoring to analyze the performance of running application but what if:
- we are not getting 100% analysis
- only got the handled error exceptions
- our applications have some anonymous errors which weren’t tracked in our system status error code and that continuously increased the load or downtime, and many more.
Will you actually debug that kind of error? How difficult is it to identify what caused Application Crash? Some organizations have set custom status codes for similar or multiple look-alike error strings but what if they are actually not similar, and you would be like “ignore, that’s our handled one we are throwing that status code”.
Continue reading “Monitoring and Release tracking with Sentry”