Search by replayID give no results on the Traces view.

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

Send a replay connected to a trace to Sentry
Open the replay
Switch to the "trace" tab.
Click "Open in Explore"

Alternatively, search for spans associated with a replay in treces using replayId:REPLAY_ID

Expected Result

The traces view returns spans, transactions or traces with the replay ID.

Actual Result

No results.

Even when the UI shows no results, I can see the replay in the trace view (EXAMPLE) and in the root span JSON, I can see the replayID:

"replay": {
"replay_id": "59b86fe65a024f2e831e4857070f18d7",
"type": "replay"
},
...
"replay_id": "59b86fe6-5a02-4f2e-831e-4857070f18d7",

Searches using both replayID and replay_id give no results on the traces page.

Link to the replay in the examples above.

Product Area

Explore

Link

No response

DSN

No response

Version

No response

ENG-7543

JAVA-491

JAVA-492

Assigning to @getsentry/support for routing ⏲️

verified in getsentry/sentry-java:

SentryReplayEvent.setTraceIds() exists in sentry/src/main/java/io/sentry/SentryReplayEvent.java, but i could not find any production replay-generation code calling it.
the only in-repo setTraceIds( call site i found is inside SentryReplayEvent.Deserializer, i.e. deserialization, not replay creation/sending.
android replay event construction in sentry-android-replay/src/main/java/io/sentry/android/replay/capture/CaptureStrategy.kt sets fields like eventId, replayId, segmentId, timestamps, replayType, and videoFile, but does not set traceIds.
searching for traceIds, setTraceIds, and getTraceIds in production sources only turned up the SentryReplayEvent model/serializer itself.

so this looks consistent with the reported behavior: android replays can be associated with a trace, but the replay event itself is not populating traceIds, which would explain why searching replayID in traces / traceID in replays does not work the same way as in browser.

if useful, i can turn this into a small sentry-java issue next.

Quick update on this.
After this change in relay, searching for a replayID in Traces is now working.

The replays are still not associated with a traceID, which makes searching for replays with a traceID not work. This issue will remain open while we work on it.

fix(replay): Populate trace_ids in replay events for trace search

fix(replay): Associate trace IDs with replay segments (#5473)

A PR closing this issue has just been released 🚀

This issue was referenced by PR #5473, which was included in the 8.43.1 release.

fix(replay): Associate trace IDs with replay segments (#5473)

Navigation Menu

Repository navigation

Search by replayID give no results on the Traces view. #5346

Environment

Steps to Reproduce

Expected Result

Actual Result

Product Area

Link

DSN

Version

A PR closing this issue has just been released 🚀

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Search by replayID give no results on the Traces view. #5346

Description

Environment

Steps to Reproduce

Expected Result

Actual Result

Product Area

Link

DSN

Version

Activity

linear-code commented on Apr 28, 2026

getsantry commented on Apr 28, 2026

sentry-junior commented on Apr 29, 2026

rodolfoBee commented on May 27, 2026

github-actions commented on Jun 3, 2026

A PR closing this issue has just been released 🚀

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions