Use Raygun's Deployment Tracking capabilities to be alerted to issues caused by bad releases.
Deployment Tracking will allow you to correlate error groups to your deployment versions. Notifying Raygun when you release your software.
You'll be able to instantly spot problematic deployments along with the commits that made up each of them. You'll then be able to see which errors occurred in the deployment version, which were fixed, and which are still occurring.
note: We’ve recently updated our Deployment Tracking to be version-based, rather than time-based. Now new errors are correlated to the deployment version they first occurred in. This means even if you have multiple versions of your application in production, you will still be able to discern which deployments are causing issues. Your error reports must include a deployment version number to be correlated to a deployment.
Once set up, new deployments and their details will appear on the Deployments page inside Raygun. You can filter these by date and time. Details of the deployment version, notes, person and time are all easily viewable. Click on the deployment version to see the details of each release.
Raygun will now display new errors that have occurred in the deployment version, any regressions and errors that are still occurring (that were happening before and after the deployment). This gives you a great view of which errors you have eliminated and which you have introduced with your latest codebase updates.
Deployment Tracking is a simple to use but powerful feature we think you're going to love, and it's super simple to set up! We have plenty of options as described below. Make sure your error reports include a deployment version number so they can be correlated to a specific deployment. Do not hesitate to reach out to us if you are having any trouble getting Deployment Tracking working with your applications.