getsentry / getsentry/sentry

Metric graphs: indicate when results come from a lower-fidelity / downsampled query tier

Open
#118,217 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

3. Medium Product Area: DDM Waiting for: Product Owner
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
21h 23m
Merged PRs (30d)
607

Description

Problem Statement

Metric time-series charts can drop to a lower-fidelity query tier (for example, when a window exceeds the row cap scanned before downsampling). This introduces variation/dips that are artifacts of the query tier rather than real signal. Today nothing on the graph indicates that a lower-fidelity tier is in use, so users interpret these artifacts as real data.

Why the current behavior is insufficient
Users cannot distinguish fidelity/sampling artifacts from genuine metric behavior. This produces repeated confusion and support questions, and undermines trust in metric values, even when the underlying alerting (which uses a shorter, full-fidelity window) is accurate.

Solution Brainstorm

Display an indicator (badge, shaded region, or legend note) on the chart when results are served from a downsampled/lower-fidelity tier, with a tooltip explaining the tier and the affected time range. Optionally surface the threshold (e.g., row cap) and which ranges are full vs. reduced fidelity.

Product Area

Alerts

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

No files, tests, or entry points are named. Start by tracing how metric chart results expose query-tier or fidelity information, then determine how the chart can receive the affected ranges; done means reduced-fidelity results are visibly indicated with explanatory context without implying genuine metric changes.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.