Pick how "related" you want to see
A dropdown at the top of the tab lets you switch between four correlation scopes:
- Trace (default): every log record and span event in the same distributed trace as this span. Best starting point for reconstructing a request.
- Resource: everything on the same service within ±30 minutes of the span. Handy when the interesting logs live outside the span's own trace context (background jobs, scheduled tasks).
- Resource & Trace: the union of the two above.
- Span: only the log records and events directly attached to this span. Same behaviour as the old "Events & Logs" tab.
The list places the span in context
Inline marker rows show exactly where "This span started" and "This span ended" sit within the surrounding stream. Older records appear below, newer above. When you paginate away and click the duration pill above the list, it snaps you back to the span-start marker. Or, if you've drifted far enough that the marker is out of the cached window, it re-fetches around the anchor and centers there.
Deep links from the trace tree still work
Clicking an event in the trace tree scrolls the list to that event and briefly highlights the row, so navigating from a span's timeline into the surrounding logs keeps your place.
Same primitive on both sides
The tab is built on the same virtualized list, cursor pagination, and row layout that the log sidebar's Related Logs tab already uses. Both sides share behaviour, keyboard focus, and infinite-scroll semantics.