getsentry / getsentry/sentry

In "Potential Causes" section of performance issues link to domain specific charts if applicable

Open
#75,068 1 comment 0 reactions 0 assignees View on GitHub
Feature Product Area: Insights
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
22h 21m
Merged PRs (30d)
586

Description

### Problem Statement

In the "Potential Causes" section of a performance issue, we link to the generic span summary page, even if the span is a well known semantic span such as `http.client`:

![Image](https://github.com/user-attachments/assets/b305029b-0972-4111-8dda-fa0ffd5dcb63)

Links to:

![Image](https://github.com/user-attachments/assets/982e77c6-c8a1-4792-b384-ccf55c323629)

If the span is a well known type with an entity page, the entity page provides additional contextual information useful to debugging the problem:

![Image](https://github.com/user-attachments/assets/4221846d-8631-465c-bc1e-fe6de8199e52)

In this specific case, the performance data also seems to tell a more interesting story, with durations remaining longer after a certain inflection point:

![Image](https://github.com/user-attachments/assets/642eb2ee-79b6-4e89-96cb-321f7e43e1d3)

### Solution Brainstorm

If there is a well known semantic span in Potential Causes, link to the entity page for that span rather than a generic span page.

### Product Area

Performance

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.