GDB (GNU Debugger) is very well suited in scenarios when the program has core dumped and a core file is generated. In such a case, the only tool that comes to my mind and can help diagnose such a core dump is GDB (GNU Debugger). GDB (GNU Debugger) is the best tool for debugging core dumps in *nix platforms. This will not be suitable for those who are very new to *nix platforms or who are earlier users of Windows platforms, as there is not any sort of GUI display or window here
Great for standard web application performance monitoring, analytics and error reporting. Shows line level code errors, gives insight into performance issues (plugins, API issues, etc.). Automation and scheduled scanning in production gives client visibility into 'after deployment' value. Also lets a relatively small number of developers keep tabs on a handful of different site/applications without needing a bunch of tools. The UI is pretty complicated and can be overwhelming for new users. Documentation could be better for the learning curve,
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.
Jira is an alternative for GDB (GNU Debugger) in bug tracking department. When compared to GDB (GNU Debugger), Jira is more expensive to initially buy. Hence GDB (GNU Debugger) is well suited for all sizes of organizations, be it a small startup company or a large multinational company. Also if the memory footprints of both are compared, GDB (GNU Debugger) has a much smaller footprint when compared to those of its competitors.
We used Rollbar but didn't like the configuration its not easy. And also doesn't support wide features like Sentry although its a cheaper option but doesn't have the dash-boarding like Sentry and its was not easy to integrate webhooks for different purposes. Somehow many people in company where not able to understand Rollbar dashboard who were very much used to Sentry.
We had to take it down later due to internal reasons and majorly because of cost-cutting process
If someone has a unstable system and have no way to figure out what to do, can use sentry at least temporarily along with some other APM to fix their system faster
