getsentry / getsentry/sentry

Add span_id as a first-class filter in the Logs explorer

Open
#110,512 4 comments 0 reactions 0 assignees View on GitHub
Feature Product Area: Explore
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
21h 10m
Merged PRs (30d)
635

Description

### Problem Statement

Currently, the Logs explorer supports filtering by `trace_id`, which returns all logs across an entire trace.

However, there is no straightforward way to filter logs scoped to a specific span within that trace.
When diagnosing slow requests, it is often necessary to isolate logs associated with a single span so please consider adding `span_id` as a first-class, suggested filter attribute in the Logs explorer, alongside `trace_id`.

### Solution Brainstorm

_No response_

### Product Area

Explore

Contributor guide

Open the contributing guide

Research direction

Start by tracing how the Logs explorer currently exposes and applies the trace_id filter, including any tests for suggested filter attributes. Determine where span_id should be added alongside trace_id and verify that filtering scopes results to the selected span. Done means span_id is a first-class suggested filter in Explore and its behavior is covered by tests.

Written by the indexing model from the issue text.

Assessment

Domain
observability
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.