getsentry / getsentry/sentry

Transactions are missing from the trace details page

Open
#107,841 7 comments 0 reactions 1 assignee Assigned to @nsdeschenes View on GitHub
Product Area: Explore
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
21h 10m
Merged PRs (30d)
635

Description

Image
Image

### Self-Hosted Version

26.1.0

### CPU Architecture

x86_64

### Docker Version

28.0.4

### Docker Compose Version

2.34.0

### Machine Specification

- [x] My system meets the minimum system requirements of Sentry

### Installation Type

Upgrade from 25.4.0 TO 25.5.1 TO 26.1.0

### Steps to Reproduce

The problem occurs when I navigate to the trace details page (from the discovery page, for example) displaying the transactions of a distributed trace. The transaction I selected is in focus. A distributed trace consists of several projects, with multiple transactions running on each project.

### Expected Result

I see all transactions related to this distributed trace.

### Actual Result

Depending on which transaction is in focus, I see a different set of transactions. The focused one is always present. But I usually don't see some of the other transactions, and only occasionally do I see all of them. If I select other transactions in this trace to be in focus and refresh the page, the set of transactions displayed changes. But it consistently changes to the same one. The transactions I see when a particular transaction is selected will be consistently displayed with each request. If I remove the focus (by editing the request parameters in the URL), I can consistently see all transactions. I don't see any parent-child or sibling specific behavioral. Both child and sibling transactions may be missing.

For example, these two queries (which are executed on the page) return different sets of transactions. Same trace, different targetId. Responses attached
```
Request1: /api/0/organizations/myorg/events-trace/6ddfbcfc8d391f50303e09a19f41e044/?limit=10000&targetId=7f6962739a714cc4a3be3ce2c250b398×tamp=1768850446

Request2: /api/0/organizations/myorg/events-trace/6ddfbcfc8d391f50303e09a19f41e044/?limit=10000&targetId=74691caf7a634694923c1ce71ca97bee×tamp=1768850446
```

[request2_response.txt](https://github.com/user-attachments/files/24723679/request2_response.txt)
[request1_response.txt](https://github.com/user-attachments/files/24723678/request1_response.txt)

### Event ID

_No response_

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.