We all have known bugs and we don't necessarily want to fix all bugs before releasing a new version. Especially not if we are running continuous deployment or similar release processes. Being able to determine if a release is causing new errors or just logs previously known bugs, is one of the great benefits of Deployment Tracking.
The New error metric shows how many errors that each release introduced. Watching a list of errors is available by clicking the New error metric, which will take you straight to the rich elmah.io error view, that you already know and love.
Interesting metrics like the number of users and browsers that are affected by a new release, are available on the Deployment Tracking dashboard. The metrics will give your DevOps engineers the perfect tool to follow-up on deployments.
Nobody likes a blame game. But when a bug is introduced, being able to determine what caused the error, can make a big difference. Fixing recently introduced bugs fast can mean life or dead of most online products today.
With the source code integration, we automatically pull the changelog from your deployment product like Azure DevOps or Octopus Deploy. You can even use elmah.io Deployment Tracking as your main list of releases and what's in them.
Finally, our integrations pull information about who triggered each deployment. In cases where people are actually involved, you know who to talk to first, when errors starts to roll into your logs.