getsentry / getsentry/sentry

Support Usage Mode in new Trace Explorer to make it easier to track Span Consumption

Open
#89,266 11 comments 0 reactions 0 assignees View on GitHub
Product Area: Performance
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
21h 10m
Merged PRs (30d)
635

Description

### Environment

SaaS (https://sentry.io/)

### What are you trying to accomplish?

I have following two questions

## Need clarity on span calculation and how is counted for costing
I am trying to evaluate the overall span usage by different category and operation for specific time period,
Here I am checking for the last 30 days.

As you can see on the traces pages over overall span count look going >9M (by doing sum of all span categories) while when I see it on the Stats dashboard it shows Span usage as 3.5M.

I don't understand how span is calculated here, which span are getting calculated in costing.

![Image](https://github.com/user-attachments/assets/4eea25e4-d0d2-4b42-8ae5-2b5edee71221)

![Image](https://github.com/user-attachments/assets/e80d7dd7-ddd2-455f-8408-9d202234d1e8)

## As you can see there are multiple span are getting created with `mark`, `measure`, `ui.long-animation-frame` Is this getting used in any metric evaluation of insights and can I discard this with `tracingSampler` to save a span usage ?

![Image](https://github.com/user-attachments/assets/f2538343-9f34-4ecf-ac04-3e4cf6a1def7)

### How are you getting stuck?

Yes, We are planning to introduce Tracing and Performance monitoring on all product lines, but we are not able to calculate the total costing and usage due to this discrepancy

### Where in the product are you?

Performance

### Link

_No response_

### DSN

_No response_

### Version

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the new Trace Explorer and the Stats dashboard for the reported 30-day span-count discrepancy. Trace how span categories, operations, and spans such as mark, measure, and ui.long-animation-frame are represented, then define the Usage Mode behavior and verify that costing and sampling guidance answer the reported questions.

Written by the indexing model from the issue text.

Assessment

Domain
analytics, observability-sre, performance
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.