Interaction between “Visualize” percentile and “Choose Your Metric” dropdowns
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 23m
- Merged PRs (30d)
- 607
Description
When configuring a metric monitor, the relationship between the “Visualize” percentile dropdown and the “Choose Your Metric” dropdown could be clearer? Changing one control currently causes the other to update automatically, which can make it hard to tell exactly what is being visualized.
For example:
- Selecting p75 in “Visualize” forces “Choose Your Metric” to change from “Largest Contentful Paint” to “Custom”.
- Selecting “Largest Contentful Paint” again forces “Visualize” back to p95.
- This makes it appear that changing the percentile is also changing the underlying metric/profile, but this relationship is not explained anywhere in the UI.
If certain metrics are only valid at specific percentiles, the UI should explain this (e.g., via labels or tooltips), instead of having dropdowns that change each other without explanation.
There could be a clearer mental model of:
When they are only changing a percentile on the same metric vs. When they are switching to a different metric/profile entirely.
https://github.com/user-attachments/assets/a3963169-b955-420a-bb31-1751c342844c
The hidden coupling between the two dropdowns makes the configuration feel unpredictable and “fights” user intent.
As it can make people think there is a bug in the UI preventing this specific configuration.
However, it was noted that the search term wouldn't work because it's in measurements.
Potential improvements / ideas
- Make the relationship between the percentile and metric/profile explicit in the UI (e.g., helper text or tooltip explaining why a given percentile forces a specific metric/profile).
- Show a short summary of “what you are visualizing” (e.g., “Visualizing: Largest Contentful Paint, p95”) near the chart so users can quickly confirm the final state.
- State measurement improvements
Product Area
Metrics
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by reproducing the metric monitor flow described in the issue, changing “Visualize” and “Choose Your Metric” in both directions; done should make the relationship explicit and let users confirm the final metric and percentile without the controls appearing to fight their intent.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100