getsentry / getsentry/sentry

Allow parent spans to display logs from all child spans within the trace hierarchy

Open
#101,875 6 comments 0 reactions 0 assignees View on GitHub
Explore > Logs Product Area: Explore
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
22h 21m
Merged PRs (30d)
586

Description

### Problem Statement

Currently, when viewing a span in the trace view, the Logs panel only shows entries emitted directly within that span (trace.parent_span_id = span ID). Logs from nested or child spans do not appear in the parent’s Logs panel, making it difficult to view a complete picture of activity for an endpoint or transaction with multiple sub-operations.

### Solution Brainstorm

When a user selects a parent span, automatically include logs from all descendant spans in the Logs panel.
To make this clear:
- Visually differentiate direct vs. inherited logs.
- Optionally include a toggle (“Show logs from child spans”).

### Product Area

Explore

Contributor guide

Open the contributing guide

Research direction

Start in the Explore trace view and inspect how the Logs panel currently filters entries to the selected span. Define how descendant spans are identified, how direct and inherited logs are distinguished, and whether a child-log toggle is needed; done means selecting a parent shows the agreed logs from its trace hierarchy.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
observability-sre
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.