getsentry / getsentry/sentry

Match Dashboard widget units with Discover units (ms vs s)

Open
#90,095 9 comments 1 reaction 0 assignees View on GitHub
2. High Feature Product Area: Dashboards
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
22h 21m
Merged PRs (30d)
586

Description

### Problem Statement

When passing custom measurements with a defined unit, such as `second` based on these docs ([Sending Performance Metrics](https://docs.sentry.io/platforms/python/tracing/span-metrics/performance-metrics/)), they show up properly on the Discover page's Bar Graph. But on the bar graph in Dashboards, they always seem to display in milliseconds even thought the table below it displays the units.

**Screenshot of graph in Discover (I'm sending 2 measurements of `second` and 1 measurement of `millisecond`)-**

Image

**My Dashboard Widget -**

Image

[Link to my Discover](https://francisorg.sentry.io/discover/results/?id=32327&project=-1&statsPeriod=1h)

[Link to my Dashboard](https://francisorg.sentry.io/dashboard/125311/widget/2/?statsPeriod=7d)

### Solution Brainstorm

We should make them match when the unit is provided.

### Product Area

Dashboards

Contributor guide

Open the contributing guide

Research direction

Use the linked Discover and Dashboard views to reproduce the same custom measurements with second and millisecond units, then compare the bar-graph formatting with the table. The work is done when the Dashboard graph matches Discover's unit handling while the table continues to display correct units.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data-visualization
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.