![\"\"](\"https:\/\/opstree.com\/blog\/\/wp-content\/uploads\/2022\/09\/pic1.png?w=279\")
<\/figure>\n\n\n\nWill 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 \u201cignore, that’s our handled one we are throwing that status code<\/em>\u201d.<\/p>\n\n\n\n\n\n\n\n Yes, I know you all are thinking that there are many monitoring tools that will tell you the exact problem but what if they don\u2019t provide you with a stack trace? You will be confused, right. Many applications have the power of analysing the bugs in depth but you will have to put more and more effort into doing this.<\/p>\n\n\n\n No more mindlessly pasting errors on the internet. That\u2019s why Sentry comes in a picture that is simple to use and the issues come directly from the code end.<\/p>\n\n\n Sentry<\/strong> Introduction<\/strong><\/p>\n\n\n\n Sentry is an open-source, cross-platform error tracking tool that helps developers to monitor, and fix crashes in real-time. Its major features help in boosting efficiency and improve the user experience like tracking and detecting every possible exception from its SDK; whether it is handled by you or the code block. It has support for almost all programming languages. <\/p>\n\n\n\n It is extremely easy to set up as it gives SDK to integrate into your code and every exception that lies under that SDK will occur on the sentry.io<\/strong> dashboard. It’s vital as it helps in avoiding errors that our application might pass on silently. It detects and tells you in which backend file you have the issue. With that, it covers the overall details of every new exception, old exceptions, their occurrences, and many more. Also, you have the admin power to assign anyone on that issue to keep the records who will solve that. It does also help us in keeping our application stable and optimized. <\/p>\n\n\n\n Sentry is available as a self-hosted version or a paid, cloud-hosted option, which makes it really versatile for various types of businesses.<\/em><\/p>\n\n\n\n So, here is one of the features of the sentry which is very powerful and help organizations track their deployments on a daily, monthly, and yearly basis.<\/p>\n\n\n\n So, I\u2019m talking about the release tracking feature in which you will find your:<\/p>\n\n\n\n 1. Application health<\/p>\n\n\n\n 2. Commits details<\/p>\n\n\n\n 3. Author details<\/p>\n\n\n\n 4. Changed files<\/p>\n<\/div>\n\n\n\n So in release tracking, the release is a version of your code deployed to an environment in that time you have to notify Sentry about a release which helps the developer to identify new issues and regressions, determine whether an issue is resolved in the next release, and apply source maps or other mapping files. The Releases <\/strong>page provides a visualization of your releases. It presents the adoption of releases from the past 24 hours and provides a high-level view of:<\/p>\n\n\n\n 1. Each release version<\/p>\n\n\n\n 2. The associated project<\/p>\n\n\n\n 3. The adoption stage of each release<\/p>\n\n\n\n 4. The authors of each commit<\/p>\n\n\n\n 5. The percentage of crash-free users<\/p>\n\n\n\n 6. The percentage of crash-free sessions<\/p>\n\n\n\n <\/p>\n<\/div>\n\n\n\n <\/p>\n\n\n\n Notifying Sentry of a release enables auto-discovery of which commits to associate with a release and identifies the most recent release when searching in sentry.io<\/a><\/p>\n\n\n\n Each release links to one or more projects. If a release has multiple projects, Sentry will duplicate the release data in relation to each one.<\/p>\n\n\n\n Also, releases offer significant additional features when fully configured:<\/p>\n\n\n\n We can determine the issues and regressions introduced in a new release which do the following,<\/p>\n\n\n\n We recommend notifying Sentry about a new release before deploying it. But if you don\u2019t, Sentry will automatically create a release entity in the system the first time it sees an event with that release identifier.<\/p>\n\n\n\n Sentry supports demangling of transpiled, minified, and bundled JavaScript using source maps, which are JSON files that contain information about how to map your deployed code back to its original source so that you can view source code context obtained from stack traces in its original form. Releases are required to apply source maps<\/a> or other debug files to follow the same. This is useful for debugging files that are processed, ie.. bundled, minified, transpiled, compiled, or otherwise obfuscated by tools like Webpack, Terser, or the C++ compiler \u2014 from a higher-level language.<\/p>\n\n\n\n You can identify\u00a0suspect commits in the <\/em>release track, which helps you to detect or analyze which author\u2019s commit caused an issue. Sentry uses commit metadata from your source code repositories to identify the suspect commits.<\/p>\n\n\n\n This all can be viewed under the Issue Details page to view suspect commits as well as the list of authors of those commits. We can also assign or alert the issue owner, based on your organization’s ownership rules.<\/p>\n\n\n\n Release health<\/em> shows and provides insights into the impact of crashes and errors as it relates to your user’s experience and changes trends with each new issue.<\/p>\n\n\n\n We can monitor release health by,<\/p>\n\n\n\n You can also explore the health of a release more closely on the\u00a0Release Details<\/a>\u00a0page.<\/p>\n\n\n\n The Release Details<\/strong> page focuses on an individual release. Elements of the release are displayed, such as visualized trends for crashes and sessions, specifics regarding each issue, adoption graphs, and commit author breakdowns.<\/p>\n\n\n\n Also, you can find the no.of deploys of each release and see the issues related to that deploy id, which helps you identify which release has a major problem.<\/p>\n\n\n\n The graph at the top provides insights into the health of your release by allowing you to choose which metric it displays. The metrics that can be shown totally depend on the amount of data metric you want. Like in the above picture I\u2019ve only enabled these metrics for release tracking.<\/p>\n\n\n\n But if all metrics are enabled then select the time range that you want to review and choose from these metrics in the table below the graph:<\/p>\n\n\n\n <\/p>\n\n\n\n If you want to know which errors are from which production release name associated, you can easily find this<\/p>\n\n\n\n For release track setup in 4 simple steps please reach out to this<\/strong> And for more information regarding this tool, you can access this <\/strong> The purpose of this blog was to dig a little deeper into monitoring concepts of this tool and its wonderful features which helps to enhance the application system. It’s not just the monitoring but the exceptions tracking tool. Here I’ve explained how we would get the exact cause of that bug in less time. In release tracking, it’s very helpful for both developers and DevOps to identify the exact cause of the incoming issues in new releases. They can find out from which files and commits it happened and who’s the main culprit of that bug in different releases. It is easy for developers to view every record of deployment release.<\/p>\n\n\n\n Next time we will meet with some new tool concepts.<\/p>\n\n\n\n Blog Pundits: Naveen Verma<\/a> and Sandeep Rawat<\/a><\/strong><\/p>\n\n\n\n Opstree<\/a><\/strong>\u00a0is an End to End DevOps solution provider.<\/p>\n\n\n\n![\"\"](\"https:\/\/opstree.com\/blog\/\/wp-content\/uploads\/2022\/09\/pic2.png?w=300\")
<\/figure><\/div>\n\n![\"\"](\"https:\/\/opstree.com\/blog\/\/wp-content\/uploads\/2022\/09\/pic3-2.png?w=225\")
<\/figure><\/div>\n\n\n![\"\"](\"https:\/\/opstree.com\/blog\/\/wp-content\/uploads\/2022\/09\/1_bp6jyilpc3ohlfmabapl-w-1.png?w=700\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/opstree.com\/blog\/\/wp-content\/uploads\/2022\/09\/pic4.png?w=1024\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/opstree.com\/blog\/\/wp-content\/uploads\/2022\/09\/pic5.png?w=1024\")
\n
Apply Source Maps or Other Debug Files<\/strong><\/h5>\n\n\n\n
Enable Suspect Commits<\/strong><\/h5>\n\n\n\n
![\"\"](\"https:\/\/opstree.com\/blog\/\/wp-content\/uploads\/2022\/09\/pic6.png?w=1024\")
<\/figure>\n\n\n\nTrack Release Health<\/strong><\/strong><\/h5>\n\n\n\n
\n
Release Details<\/strong><\/h5>\n\n\n\n
![\"\"](\"https:\/\/opstree.com\/blog\/\/wp-content\/uploads\/2022\/09\/pic7.png?w=1024\")
<\/figure>\n\n\n\n\n
![\"\"](\"https:\/\/opstree.com\/blog\/\/wp-content\/uploads\/2022\/09\/pic8.png?w=940\")
![\"\"](\"https:\/\/opstree.com\/blog\/\/wp-content\/uploads\/2022\/09\/pic9.png?w=736\")
![\"\"](\"https:\/\/opstree.com\/blog\/\/wp-content\/uploads\/2022\/09\/pic10.png?w=402\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/opstree.com\/blog\/\/wp-content\/uploads\/2022\/09\/pic11.png?w=1024\")
link:<\/strong> https:\/\/docs.sentry.io\/product\/releases\/setup\/<\/a><\/p>\n\n\n\n
link:<\/strong> https:\/\/docs.sentry.io\/product\/releases\/<\/a><\/p>\n\n\n\nConclusion<\/strong><\/h5>\n\n\n\n