Rules to Better RayGun

Hold on a second! How would you like to view this content?
Just the title! A brief blurb! Gimme everything!

​​​​RayGun is a paid cloud based application monitoring product that does Crash Reporting and User Monitoring for your web or mobile application. Raygun makes triaging and reporting exceptions in your application easy by grouping the exceptions and tracking them against deployments so you can easy see if they are new exceptions, recurring exceptions or regressions.​

Check out the video below to see how you can use RayGun as part of your DevOps.​


  1. Do you know how to handle errors in Raygun?

    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 (TFS/

    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

    Hi Adam,
    Please find below the Raygun Health Check for TimePro:

    Figure: Raygun health check for TimePro in the past 7 days 


    Figure: Resolved issues in the past 7 days​


    Figure: The next issue to be worked on​

    <This email is from >​

    Figure: Email with Raygun application health report​​​ 

  2. Do you know how to integrate RayGun with VisualStudio/TFS?

    TFS/ is the source of truth for product development, so how do you get issues in RayGun into TFS? Thankfully there’s a built in integration that lets you do that. 
    1. Under Integrations
    2. Select Visual Studio Team Services
    3. Connect to your TFS or instance
    Figure: Link RayGun with TFS/

    Now under the crash report, you have to option to create a PBI and link it to the crash report.

    Figure: Create a new PBI or link to an existing PBI

    Now you can see which RayGun create reports have already been added to the backlog.

    Figure: Link RayGun with TFS/

    RayGun is a useful tool to use for your DevOps. Check out our rule “Do you know how DevOps fits in with Scrum?​​”​​

  3. Do you know how to integrate RayGun with Octopus Deploy?

    One of the best features of RayGun is the ability to track crash reports against deployments. This feature allows you to tell if a particular deployment has introduced a lot of new bugs or caused a regression of exceptions. ​

    To set it up:​

    1. Under Deployments
    2. Select Octopus Deploy (Set up)

      Raygun will product you with a PowerShell script to add into your octopus deployment steps that will call the RayGun API and log a new deployment

    3. Trigger a new deployment
    4. Then you’ll see the deployment in RayGun

      Drilling into a deployment you’ll see:

      • New errors
      • Regressions
      • Recurring errors
      Figure: Good Example – Now you can measure the quality of your deployments
  4. Do you know what errors to filter out?

    You should always keep on top of your RayGun crashreporting and not let the errors spiral out of control. If use RayGun with a web application, then you’ll frequently get a lot of errors with robots scanning the site and creating 404s.
    Figure: Bad Example – Most of these errors are 404s cause by automated tools scanning for vulnerabilities

    Luckily RayGun has built-in filtering to hide these frequent exceptions.


    To enable filtering:

    1. Under Crash Reporting > select Filtering
    2. SSW recommends you turn on the following rules
      1. Discard any requesters where the user-agent is a known crawler bot
      2. Discard any request for non-existent resources (404)
      3. Discard any requests related to phpMyAdmin access attempts

    Now you should have a nice clean crash report page with actual errors.

    Figure: Good example – Now that the noise is gone, we can see the actual errors