getsentry / getsentry/sentry

Some high-cardinality tags hide a value in the Tag Details UX

Open
#94,727 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Bug Product Area: Issues
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

We have one tag on a particular issue that seems to hide one of the values in the UX. This same tag on other issues loads ok, and we haven't seen any other issues/tags with this problem in our spot checking, even those with many unique values. The tag in question has 10.6k distinct values on the problematic issue.

This is reproducible between several users for this particular issue & tag on our instance

Full details, including links and a recording of the problem, are available on the internal customer case

  1. Open one of the problematic issues
  2. Click "View All Tags & Flags" (it might be "View all tags and feature flags" as well depending on UX version or distribution or something?)
  3. Observe that the problematic tag has a top value of X, with %x, and the second highest value of Y with y%. In our example, it's 65%, 34%, <1% for the third value, and then Other: 1%, and tag name of bucket_id
  4. Click on the tag to view full details, which opens the "Tag Details - $tag_name" pane.
Expected Result

The details should show the same X, Y, and following tag values with the correct % and counts

Actual Result

The details miss X, and display only Y and below. It uses the same y% as before, so in our example the Share does not add up to 100%

NOTE: the network request to https://us.sentry.io/api/0/organizations/$org/issues/$issue/tags/$tag_name/ does return X, so it seems like a UX problem.

Product Area

Issues

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 with the “View All Tags & Flags” entry point and the “Tag Details - $tag_name” pane for the issue tag view. Compare the tag-details rendering with the response from /api/0/organizations/$org/issues/$issue/tags/$tag_name/, which includes the missing top value. Done means the pane displays that value and the following values with correct counts and percentages totaling 100%.

Written by the indexing model from the issue text.

Assessment

Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.