Announcing an all new stack trace design for Raygun Crash Reporting

| 2 min. (300 words)

Raygun Crash Reporting has a whole new stack trace design. We’ve now made it easier than ever to drill down into the exact line of code in which an error occurred.

The stack trace (also known as the back trace) is one of the most important parts of the Raygun application, and has been crucial to our customers since day one.

We decided it was time to refresh the design and upgrade the functionality to help you find the source of the problem faster.

Improvements made include:

Updated design for easier readability
We decluttered the code so you can focus on what’s causing the issues.

Grouping of stack lines from common libraries (e.g. System in ASP.NET)
These are collapsible, which helps developers to easily focus on the important stack data.

Collapsible code snippets and local variables for JavaScript and Python
Before, these were always expanded. Now, it’s easier to see which lines are affected.

What it looks like by language


Raygun's stack trace design for C#


Raygun's stack trace design for JavaScript


Raygun's stack trace design for Python

Where to find the new stack trace

You will still find the stack trace in the same place. When you receive an error notification in your Raygun Dashboard, head to the Error Instance, then ascertain exactly where in your code base that the error is stemming from using the latest stack trace design.

Have questions about the latest stack trace design?

Get in touch with a friendly team member here.

Without the Raygun Software Intelligence Platform, if an error occurs on a server, the precious stack trace can vanish and be lost forever. You would either to have to dig through logs to determine what has caused the problem, or worse, the error would go unnoticed and continue to affect users.

Now read:

Architecting software errors for better reporting

5 tips for writing great software error messages