Sentry Error detail page in GitLab

Problem to solve

We want to display pertinent details of Sentry errors in GitLab to reduce time spent switching tools and context. Users will be fixing the error via GitLab, so as much review and work as we can keep in GitLab's interface, the more time we save the user.

We want to avoid completely rebuilding errors in GitLab, as this has already been done in Sentry. The goal is to provide enough pertinent information that a user can decide if the error is critical enough to create an issue for.

Intended users

• Delaney (Development Team Lead)
• Sasha (Software Developer)
• Devon (DevOps Engineer)
• Sidney (Systems Administrator)

Further details

This work supports the Error Tracking Vision.

Proposal

Create a specific for an error that can be accessed from the error list. It will open in a new page.

WIP design

Error detail view

Permissions and Security

Documentation

Documentation required, most likely here.

Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Links / references