getsentry / getsentry/sentry

Enhance Extrapolation Descriptino with Discover Engine

Open
#119,670 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Improvement Product Area: Explore
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
21h 23m
Merged PRs (30d)
607

Description

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

Additional wording/information regarding extrapolation ( when enabled ) would better users' understanding of telemetry they are viewing. Users consistently see the differences between volume that is extrapolated by default or in a query vs project/organization usage volumes and get confused.

Expected Result

Additional information/UI on Estimated from X.X M spans detailing extrapolation; how it's calculated & how to toggle at bare minimum.

Actual Result
Image
Product Area

Explore

Link

No response

DSN

No response

Version

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in the Explore UI where the “Estimated from X.X M spans” message appears, using the attached screenshot and the described extrapolation confusion as the entry point. Review how extrapolation is currently presented and make the calculation and toggle behavior understandable to users; done means the UI explains the estimate and how to change it.

Written by the indexing model from the issue text.

Assessment

Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.