getsentry / getsentry/sentry

View transaction tags at span level

Open
#89,454 3 comments 1 reaction 0 assignees View on GitHub
Waiting for: Product Owner
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
22h 21m
Merged PRs (30d)
586

Description

### Problem Statement

In the trace explorer, there is currently no way to surface tags such as `browser` at the span level. This prevents us from being able to see span metrics by browser type, device class, etc without manual instrumentation.

### Solution Brainstorm

Add `root` property to span that contains all parent transaction tag values. We could then aggregate on `root.browser` at the span level for example.

### Product Area

Performance

Contributor guide

Open the contributing guide

Research direction

Start by tracing how the trace explorer represents span and parent transaction tags; the issue names no files, tests, or entry points. Define how a span-level root property should expose parent transaction tags, then verify that aggregations such as root.browser work for browser and device-class values.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.