getsentry / getsentry/sentry

Metric detail view: show the current equation's calculation, and fix chart panel that cannot be scrolled

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

Nobody has claimed this yet.

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

Description

Problem Statement

On a saved metric's detail view, the chart renders against the equation as it was historically defined. Users expect to also see what the metric evaluates to under its current equation, but that current calculation is not clearly surfaced. Compounding this, the area where users expect to scroll to reach that information cannot be scrolled at all.

Why the current behavior is insufficient
After editing a metric, users have no clear way to confirm the metric is now computing what they intend. The missing "current" view plus an unscrollable panel means expected content is effectively hidden, leaving users unsure whether their change took effect.

Solution Brainstorm

Clearly distinguish and label a "historical (as-defined)" series vs. the "current equation" calculation, or provide a toggle between them. Separately, fix the detail/chart panel so it scrolls and all content is reachable (this part is likely a UI bug).

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

Start at the saved metric detail view and reproduce the behavior after editing a metric: inspect the chart panel where scrolling fails and identify how the displayed equation is selected. Done means users can reach all detail content and can clearly distinguish the historical series from the calculation under the current equation.

Written by the indexing model from the issue text.

Assessment

Domain
analytics, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.