Do you know how to handle errors in Raygun?

Last updated by Tiago Araújo [SSW] 5 months ago.See history

Your team should always be ensuring that the health of the application is continually improving.

The best way to do that is to check the exceptions that are being logged in the production application. Every morning, fix the most serious bug logged over the last week. After it is fixed then email yesterday's application health to the Product Owner.

There's traditional error logging software like Log4Net or Elmah, but they just give you a wall of errors that are duplicated and don't give you the ability to mark anything as complete. You'll need to manually clear out the errors and move them into your task tracking system (Azure DevOps/

This is where RayGun or Application Insights comes into the picture. RayGun gives you the following features:

  • Grouping exceptions
  • Ignoring/filtering exceptions
  • Triaging exceptions (mark them as resolved)
  • Integrations to TFS/ to create a Bug, Slack
  • Tracking the exceptions to a deployment
  • See which errors are occurring the most often

Figure: Bad example - Elmah gives you a wall of exceptions and no way to flag exceptions as completed

Figure: Good example - Email with Raygun application health report

We open source. Powered by GitHub