Wire bug reports into Sentry telemetry (errors, traces, replays by user)

[sentry-junior]

Summary

When junior surfaces a bug report or handles a user-reported issue, it should be able to query Sentry's own telemetry to find correlated signals — errors, traces, and session replays — scoped to the reporting user. This closes the loop between a complaint in Slack and the actual observable evidence in Sentry.

Current Behavior

• junior can create and manage GitHub issues and Slack artifacts.
• There is no integration with Sentry's API or explore/replay surfaces.
• Bug investigation requires a human to manually open Sentry and search for the relevant user/session.

Gap / Opportunity

• Reported bugs often have replay, error, or trace evidence already in Sentry — finding it is manual and slow.
• Automating the lookup (e.g. search by user.email or username) dramatically speeds up triage.
• junior already has context on who filed the report, making it the right place to trigger the lookup.

Prior Art

• Sentry Explore API supports filtering replays, errors, and traces by user attributes (e.g. user.email:david@sentry.io).
• Billy Vong manually found a replay via /explore/replays?query=user.email:david@sentry.io that confirmed a bug in ~seconds — this should be automatic.

Options

• Option A — Read-only Sentry API integration: junior queries the Sentry API (issues, replays, traces endpoints) scoped to a user and returns matching results inline in Slack.
• Option B — Deep-link generation only: junior constructs and posts pre-filled Sentry Explore URLs for the reporter's email without making API calls. Lower fidelity but zero auth overhead.
• Option C — Hybrid: generate deep links immediately, then optionally fetch top results via API if a Sentry credential is available.

Recommended Direction

Option C — generate deep links immediately (zero friction) and layer in API results when credentials are scoped. Start with Option B as an MVP.

Acceptance Criteria

• Given a bug report thread with a known reporter, junior can search Sentry for errors linked to that user.
• junior surfaces replays filterable by user.email for the reporter.
• junior links or embeds trace results correlated to the reported timeframe/user.
• Results are returned inline in the Slack thread, not as a separate manual step.

Risks

• Sentry API credential scoping — needs read access to the right org/project without leaking cross-tenant data.
• Replay privacy — surfacing replays for arbitrary users requires care; scope to internal (sentry.io) users initially.

Sources

• Thread replay example: https://sentry.sentry.io/explore/replays/f227108c7e3c45c1a6002d80f9fafc62/?query=user.email%3Adavid%40sentry.io
• Sentry Explore docs: https://docs.sentry.io/product/explore/