[betegon]

Inspecting an issue tag distribution currently requires a raw API request. Add sentry issue tags <issue> <key> so agents can compare releases, servers, or browsers using the same issue IDs, URLs, and selectors as other issue commands. Recovery commands preserve the tag key and environment.

Uses the public tag-details endpoint to return up to nine top values, with an optional single environment. Human output shows shares of all retained events and the undisplayed remainder; JSON preserves the API response and nulls. Unsupported time/search/pagination flags are rejected, and tag text is sanitized before terminal rendering. Includes command/API/SDK regression coverage and generated docs and skill references.

Examples

Compare releases for an issue in production:

sentry issue tags my-org/FRONT-ABC release --environment production

Illustrative output using synthetic data:

release — top values

Total retained events: 100

VALUE               EVENTS  SHARE
2.4.0               70      70.0%
2.3.1               20      20.0%
(empty or missing)  10      10.0%

Issue: FRONT-ABC. Environment: production. Scope: retained events.

The percentages use all retained events as the denominator, including events without a release value. When the top values do not cover every event, human output also reports the undisplayed remainder.

Inspect servers for the issue selected by @latest:

sentry issue tags @latest server_name

Read a browser distribution as JSON and select the aggregate fields for an agent:

sentry issue tags my-org/FRONT-ABC browser.name --json --fields key,totalValues,topValues

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
sentry-local	Skipped		Oct 23, 2026 8:39pm UTC