Updates to Error Group detail pages

This past week, we focused on making the detail pages for Error Groups better.

The biggest change is the way we display stack traces. Previously, the stack trace on an Error Group detail page was always from the first occurrence. That changes on the updated detail page:

Error Group detail page

You have always been able to see stack traces for individual occurrences, but now it is easier to do so directly from the Error Group detail page.

This change also makes it easier for you to drill through other data from your occurrences, all from the detail page.

Other changes include:

  • When disabling alarms for an Error Group, it is now forced into a state of OK. No more notifications for alarms being called off, after you have already disabled alarms for the Error Group.
  • For long messages, we now give you the option of expanding them to see the full message, rather than just displaying all of it. (A 22,000+ character long message of our own was a great nudge to get this done.)
  • A slight change in our timestamps across the site. You should not notice too much—hopefully it just gives you a better understanding of when stuff is happening with your webapp.
  • Opbeat for Ruby now supports delayed_job
About the author
Mark Jensen is a product designer and code enthusiast who runs to eat.
You can follow him on Twitter or his blog.