Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion docs/guides/issues-errors.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -183,14 +183,22 @@ Learn more about <PlatformLink to="/configuration/environments/">configuring env

Some errors heavily affect power users. Others affect everyone, but rarely. Prioritize by unique user count, not just event count.

**[In Issues](https://sentry.io/orgredirect/organizations/:orgslug/issues/):** Search for `is:unresolved` and use the sort dropdown to sort by **Users**
**[In Issues](https://sentry.io/orgredirect/organizations/:orgslug/issues/):** Search for `is:unresolved` and sort by **Users** to see which issues affect the most unique users.

**What to look for:**

- Issues affecting many unique users (e.g., more than 10 users indicates widespread impact)
- Issues affecting VIP or paying users (check user tags)
- Issues blocking core workflows (login, checkout, data access)

When you open an issue, the header shows the total number of unique users affected. For more detail, review the `user` tag distribution to see:

- Unique user identifiers (user ID, email, or IP)
- How many events each user triggered
- Percentage breakdown across users

This tells you if an issue affects many users equally or if one user is stuck in an error loop.

Learn more about <PlatformLink to="/enriching-events/tags/">custom tags</PlatformLink> to mark user tiers, plans, or roles. Then search `is:unresolved user.tier:enterprise` to prioritize high-value users.

**Alert idea:** Trigger when unique user count exceeds a threshold in a time window (e.g., more than 50 users in 1 hour) to catch widespread issues.
Expand Down
Loading