Repository navigation
feat(tools): Add find_dropped_events tool for the events-dropped endpoint - #1410
Open
manessaraj wants to merge 5 commits into
Open
manessaraj wants to merge 5 commits into
manessaraj wants to merge 5 commits into
Conversation
manessaraj
force-pushed
the
sarajmanes/dain-1863-mcp-dropped-events-tool
branch
from
October 5, 2026 16:11
46bd05f to
556cbc5
Compare
manessaraj
marked this pull request as ready for review
October 5, 2026 19:35
manessaraj
force-pushed
the
sarajmanes/dain-1863-mcp-dropped-events-tool
branch
from
October 5, 2026 20:04
7eb699a to
143768d
Compare
mr-danya
pushed a commit
to mr-danya/sentry-mcp
that referenced
this pull request
Oct 6, 2026
Closes getsentry#1231. `dashboard view --sixel` now renders the complete dashboard into one Sixel canvas when terminal geometry is known, preserving the original widget grid. It renders timeseries, categorical bars, scalar values, tables, text, errors, and unsupported states with a single pixel renderer, so capable terminals never mix ASCII widgets with Sixel graphics. The command always falls back to the complete character dashboard when Sixel capability or terminal cell geometry is unavailable. The chart core remains resolution-independent, downsamples dense time series, preserves the muted gray `Other` series, and provides compact tick labels. ## Verification - `pnpm run typecheck` - `pnpm run lint` - `pnpm run test:unit` (9,260 passed; 16 skipped) Coverage includes categorical bars, scalar/table/text/error/unsupported widgets, adjacent widget positioning, dense-series tails, and the no-geometry ASCII fallback. --------- Co-authored-by: jared-outpost[bot] <jared-outpost[bot]@users.noreply.github.com> Co-authored-by: Burak Yigit Kaya <byk@sentry.io>
mr-danya
pushed a commit
to mr-danya/sentry-mcp
that referenced
this pull request
Oct 6, 2026
Closes getsentry#1231. `dashboard view --sixel` now renders the complete dashboard into one Sixel canvas when terminal geometry is known, preserving the original widget grid. It renders timeseries, categorical bars, scalar values, tables, text, errors, and unsupported states with a single pixel renderer, so capable terminals never mix ASCII widgets with Sixel graphics. The command always falls back to the complete character dashboard when Sixel capability or terminal cell geometry is unavailable. The chart core remains resolution-independent, downsamples dense time series, preserves the muted gray `Other` series, and provides compact tick labels. ## Verification - `pnpm run typecheck` - `pnpm run lint` - `pnpm run test:unit` (9,260 passed; 16 skipped) Coverage includes categorical bars, scalar/table/text/error/unsupported widgets, adjacent widget positioning, dense-series tails, and the no-geometry ASCII fallback. --------- Co-authored-by: jared-outpost[bot] <jared-outpost[bot]@users.noreply.github.com> Co-authored-by: Burak Yigit Kaya <byk@sentry.io>
mr-danya
pushed a commit
to mr-danya/sentry-mcp
that referenced
this pull request
Oct 6, 2026
Closes getsentry#1231. `dashboard view --sixel` now renders the complete dashboard into one Sixel canvas when terminal geometry is known, preserving the original widget grid. It renders timeseries, categorical bars, scalar values, tables, text, errors, and unsupported states with a single pixel renderer, so capable terminals never mix ASCII widgets with Sixel graphics. The command always falls back to the complete character dashboard when Sixel capability or terminal cell geometry is unavailable. The chart core remains resolution-independent, downsamples dense time series, preserves the muted gray `Other` series, and provides compact tick labels. ## Verification - `pnpm run typecheck` - `pnpm run lint` - `pnpm run test:unit` (9,260 passed; 16 skipped) Coverage includes categorical bars, scalar/table/text/error/unsupported widgets, adjacent widget positioning, dense-series tails, and the no-geometry ASCII fallback. --------- Co-authored-by: jared-outpost[bot] <jared-outpost[bot]@users.noreply.github.com> Co-authored-by: Burak Yigit Kaya <byk@sentry.io>
mr-danya
pushed a commit
to mr-danya/sentry-mcp
that referenced
this pull request
Oct 6, 2026
…missing env vars, new commands (#1461) ## Documentation Audit Report (2026-08-24) Weekly automated audit comparing the CLI implementation against its documentation. Changes since the last merged audit (PR getsentry#1400, 2026-08-11) include: the `sentry cli completion` command (getsentry#1427), sixel dashboard rendering (getsentry#1410), the `--environment` explore fix (#1442), and the 0.43.0 release. --- ## Findings & Fixes ### A. Undocumented or missing commands/subcommands | Command | Source | Expected doc location | Status | |---------|--------|----------------------|--------| | `sentry cli completion` | `src/commands/cli/completion.ts` (added in getsentry#1427) | `apps/cli-docs/src/fragments/commands/cli.md` | **Fixed** — added examples for bash, zsh, fish | All other commands in `src/commands/` have corresponding fragment files. Hidden backward-compat aliases (`send-event`, `send-envelope`, `bash-hook`, `whoami`, plural aliases) are correctly excluded from docs. ### B. Undocumented flags | Flag | Command | Source | Doc file | Status | |------|---------|--------|----------|--------| | `--sixel` / `-s` | `sentry dashboard view` | `src/commands/dashboard/view.ts` | `fragments/commands/dashboard.md` | **Fixed** — added example | All other non-hidden flags are auto-generated into the command docs via `generate-command-docs.ts`. ### C. Missing usage examples No new gaps. The `sentry cli completion` command was the only command without examples, now fixed. ### D. Stale descriptions | Command/Flag | Code brief | Doc description | Status | |-------------|-----------|-----------------|--------| | `sentry explore --environment` | Was: "Replay environment filter for --dataset replays" | Now works for all datasets (fixed in #1442) | **Fixed** — updated brief to "Environment filter" | ### E. Missing route mappings in skill generator **N/A** — `ROUTE_TO_REFERENCE` was removed and replaced with automatic 1:1 route-to-reference mapping via `groupRoutesByReference()` in `script/generate-skill.ts`. No manual mapping to go stale. ### F. Installation / distribution gaps No new gaps. Install script flags (`--no-modify-path`, `--no-completions`, `--no-agent-skills`) and env vars (`SENTRY_INSTALL_DIR`, `SENTRY_VERSION`, `SENTRY_INIT`) are documented in `getting-started.mdx`. Platform support table matches `.craft.yml` targets (macOS x64/arm64, Linux x64/arm64, Windows x64). ### G. Undocumented environment variables | Variable | Referenced in | Expected doc | Status | |----------|-------------|-------------|--------| | `DO_NOT_TRACK` | `src/lib/telemetry.ts` | `configuration.md` (generated from env-registry) | **Fixed** — added to env-registry.ts | | `SENTRY_PIPELINE` | `src/commands/build/upload.ts`, `src/lib/build/index.ts` | `configuration.md` | **Fixed** — added to env-registry.ts | Remaining niche/internal vars NOT added (intentionally excluded from user-facing docs): - `SENTRY_ENVIRONMENT` — bash-hook template only - `SENTRY_CLI_NO_EXIT_TRAP` — bash-hook template internal - `SENTRY_SCAN_DISABLE_WORKERS` — internal performance tuning - `SENTRY_CLI_INTEGRATION_TEST_VERSION_OVERRIDE` — test-only - `SENTRY_RN_*` — internal react-native wrapper vars - `SENTRY_TRACES_SAMPLE_RATE` — inherited from SDK, not a CLI config ### H. Auth / self-hosted gaps No new gaps. OAuth scopes in `self-hosted.md` and `DEVELOPMENT.md` are auto-generated (`GENERATED:START oauth-scopes`). The `--url` flag for `auth login` and `SENTRY_HOST`/`SENTRY_URL` behavior are documented. Token priority (OAuth > env token unless `SENTRY_FORCE_ENV_TOKEN`) is correct. ### I. Plugin/skills gaps No new gaps since the last audit. Skills install to `~/.claude` and `~/.agents` only. The `agentic-usage.md` correctly states this. Detection of other agents (Cursor, Windsurf, Copilot, etc.) is for telemetry and the docs correctly list them as "supported" agents (they can use the CLI, just not via auto-installed skills). ### J. README / DEVELOPMENT.md / contributing.md drift | File | Claim | Reality | Status | |------|-------|---------|--------| | `script/generate-docs-sections.ts` line 210 | "TypeScript types and Zod schemas" | Migrated to Valibot in getsentry#1389 (merged Aug 7) | **Fixed** | | `apps/cli-docs/src/content/docs/features.md` | DSN detection table lists 6 languages with specific `Sentry.init()` patterns | Scanner uses a universal DSN URL regex across 30+ file extensions | **Fixed** — updated table to match actual TEXT_EXTENSIONS set | Node.js version claims (v22.15+ for dev, >=20 for runtime) are correct. Build commands, test commands, and license (`FSL-1.1-Apache-2.0`) are all accurate. --- ## Top 5 Most Impactful Fixes (prioritized) 1. **DSN detection language table overhaul** (`features.md`) — The previous table implied language-specific `Sentry.init()` pattern matching, which is misleading. The universal regex approach supports 30+ file extensions. Users of Kotlin, Rust, Swift, Dart, C#, etc. would not have known their DSNs are detected. 2. **Missing `sentry cli completion` docs** (`cli.md` fragment) — New command from getsentry#1427 with no usage examples. Users discovering shell completions would miss this standalone alternative to `sentry cli setup`. 3. **Stale `--environment` flag brief** (`explore.ts`) — After #1442 fixed `--environment` to work for all datasets, the flag's `brief` string still said "Replay environment filter". Users would think it only applies to replays. 4. **Missing env vars in registry** (`env-registry.ts`) — `DO_NOT_TRACK` (industry-standard telemetry opt-out) and `SENTRY_PIPELINE` (build plugin identification) were referenced in code but absent from the generated configuration page. 5. **Zod→Valibot drift in project structure** (`generate-docs-sections.ts`) — The auto-generated project structure tree in `contributing.md` still said "Zod schemas" despite the migration to Valibot in getsentry#1389. Contributors would be confused about which validation library to use. <div><a href="https://cursor.com/agents/bc-2961de96-bee8-48d4-becb-d403a42a7cb6?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a> <a href="https://cursor.com/automations/8b0c0f35-da5e-409d-984c-5e39518ffb8a"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/view-automation-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/view-automation-light.png"><img alt="View Automation" width="141" height="28" src="https://cursor.com/assets/images/view-automation-dark.png"></picture></a> </div> --------- Co-authored-by: Cursor Agent <cursoragent@cursor.com> Co-authored-by: Miguel Betegón <miguelbetegongarcia@gmail.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: jared-outpost[bot] <jared-outpost[bot]@users.noreply.github.com>
![https://cursor.com/assets/images/open-in-web-dark.png"><source](https://cursor.com/assets/images/open-in-web-dark.png"><source){kind=link}
![https://cursor.com/assets/images/open-in-web-light.png"><img](https://cursor.com/assets/images/open-in-web-light.png"><img){kind=link}
![https://cursor.com/assets/images/open-in-web-dark.png"></picture></a> <a](https://cursor.com/assets/images/open-in-web-dark.png"></picture></a> <a){kind=link}
![https://cursor.com/assets/images/view-automation-dark.png"><source](https://cursor.com/assets/images/view-automation-dark.png"><source){kind=link}
![https://cursor.com/assets/images/view-automation-light.png"><img](https://cursor.com/assets/images/view-automation-light.png"><img){kind=link}
![https://cursor.com/assets/images/view-automation-dark.png"></picture></a> </div](https://cursor.com/assets/images/view-automation-dark.png"></picture></a> </div){kind=link}
mr-danya
pushed a commit
to mr-danya/sentry-mcp
that referenced
this pull request
Oct 6, 2026
…missing env vars, new commands (#1461) ## Documentation Audit Report (2026-08-24) Weekly automated audit comparing the CLI implementation against its documentation. Changes since the last merged audit (PR getsentry#1400, 2026-08-11) include: the `sentry cli completion` command (getsentry#1427), sixel dashboard rendering (getsentry#1410), the `--environment` explore fix (#1442), and the 0.43.0 release. --- ## Findings & Fixes ### A. Undocumented or missing commands/subcommands | Command | Source | Expected doc location | Status | |---------|--------|----------------------|--------| | `sentry cli completion` | `src/commands/cli/completion.ts` (added in getsentry#1427) | `apps/cli-docs/src/fragments/commands/cli.md` | **Fixed** — added examples for bash, zsh, fish | All other commands in `src/commands/` have corresponding fragment files. Hidden backward-compat aliases (`send-event`, `send-envelope`, `bash-hook`, `whoami`, plural aliases) are correctly excluded from docs. ### B. Undocumented flags | Flag | Command | Source | Doc file | Status | |------|---------|--------|----------|--------| | `--sixel` / `-s` | `sentry dashboard view` | `src/commands/dashboard/view.ts` | `fragments/commands/dashboard.md` | **Fixed** — added example | All other non-hidden flags are auto-generated into the command docs via `generate-command-docs.ts`. ### C. Missing usage examples No new gaps. The `sentry cli completion` command was the only command without examples, now fixed. ### D. Stale descriptions | Command/Flag | Code brief | Doc description | Status | |-------------|-----------|-----------------|--------| | `sentry explore --environment` | Was: "Replay environment filter for --dataset replays" | Now works for all datasets (fixed in #1442) | **Fixed** — updated brief to "Environment filter" | ### E. Missing route mappings in skill generator **N/A** — `ROUTE_TO_REFERENCE` was removed and replaced with automatic 1:1 route-to-reference mapping via `groupRoutesByReference()` in `script/generate-skill.ts`. No manual mapping to go stale. ### F. Installation / distribution gaps No new gaps. Install script flags (`--no-modify-path`, `--no-completions`, `--no-agent-skills`) and env vars (`SENTRY_INSTALL_DIR`, `SENTRY_VERSION`, `SENTRY_INIT`) are documented in `getting-started.mdx`. Platform support table matches `.craft.yml` targets (macOS x64/arm64, Linux x64/arm64, Windows x64). ### G. Undocumented environment variables | Variable | Referenced in | Expected doc | Status | |----------|-------------|-------------|--------| | `DO_NOT_TRACK` | `src/lib/telemetry.ts` | `configuration.md` (generated from env-registry) | **Fixed** — added to env-registry.ts | | `SENTRY_PIPELINE` | `src/commands/build/upload.ts`, `src/lib/build/index.ts` | `configuration.md` | **Fixed** — added to env-registry.ts | Remaining niche/internal vars NOT added (intentionally excluded from user-facing docs): - `SENTRY_ENVIRONMENT` — bash-hook template only - `SENTRY_CLI_NO_EXIT_TRAP` — bash-hook template internal - `SENTRY_SCAN_DISABLE_WORKERS` — internal performance tuning - `SENTRY_CLI_INTEGRATION_TEST_VERSION_OVERRIDE` — test-only - `SENTRY_RN_*` — internal react-native wrapper vars - `SENTRY_TRACES_SAMPLE_RATE` — inherited from SDK, not a CLI config ### H. Auth / self-hosted gaps No new gaps. OAuth scopes in `self-hosted.md` and `DEVELOPMENT.md` are auto-generated (`GENERATED:START oauth-scopes`). The `--url` flag for `auth login` and `SENTRY_HOST`/`SENTRY_URL` behavior are documented. Token priority (OAuth > env token unless `SENTRY_FORCE_ENV_TOKEN`) is correct. ### I. Plugin/skills gaps No new gaps since the last audit. Skills install to `~/.claude` and `~/.agents` only. The `agentic-usage.md` correctly states this. Detection of other agents (Cursor, Windsurf, Copilot, etc.) is for telemetry and the docs correctly list them as "supported" agents (they can use the CLI, just not via auto-installed skills). ### J. README / DEVELOPMENT.md / contributing.md drift | File | Claim | Reality | Status | |------|-------|---------|--------| | `script/generate-docs-sections.ts` line 210 | "TypeScript types and Zod schemas" | Migrated to Valibot in getsentry#1389 (merged Aug 7) | **Fixed** | | `apps/cli-docs/src/content/docs/features.md` | DSN detection table lists 6 languages with specific `Sentry.init()` patterns | Scanner uses a universal DSN URL regex across 30+ file extensions | **Fixed** — updated table to match actual TEXT_EXTENSIONS set | Node.js version claims (v22.15+ for dev, >=20 for runtime) are correct. Build commands, test commands, and license (`FSL-1.1-Apache-2.0`) are all accurate. --- ## Top 5 Most Impactful Fixes (prioritized) 1. **DSN detection language table overhaul** (`features.md`) — The previous table implied language-specific `Sentry.init()` pattern matching, which is misleading. The universal regex approach supports 30+ file extensions. Users of Kotlin, Rust, Swift, Dart, C#, etc. would not have known their DSNs are detected. 2. **Missing `sentry cli completion` docs** (`cli.md` fragment) — New command from getsentry#1427 with no usage examples. Users discovering shell completions would miss this standalone alternative to `sentry cli setup`. 3. **Stale `--environment` flag brief** (`explore.ts`) — After #1442 fixed `--environment` to work for all datasets, the flag's `brief` string still said "Replay environment filter". Users would think it only applies to replays. 4. **Missing env vars in registry** (`env-registry.ts`) — `DO_NOT_TRACK` (industry-standard telemetry opt-out) and `SENTRY_PIPELINE` (build plugin identification) were referenced in code but absent from the generated configuration page. 5. **Zod→Valibot drift in project structure** (`generate-docs-sections.ts`) — The auto-generated project structure tree in `contributing.md` still said "Zod schemas" despite the migration to Valibot in getsentry#1389. Contributors would be confused about which validation library to use. <div><a href="https://cursor.com/agents/bc-2961de96-bee8-48d4-becb-d403a42a7cb6?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a> <a href="https://cursor.com/automations/8b0c0f35-da5e-409d-984c-5e39518ffb8a"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/view-automation-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/view-automation-light.png"><img alt="View Automation" width="141" height="28" src="https://cursor.com/assets/images/view-automation-dark.png"></picture></a> </div> --------- Co-authored-by: Cursor Agent <cursoragent@cursor.com> Co-authored-by: Miguel Betegón <miguelbetegongarcia@gmail.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: jared-outpost[bot] <jared-outpost[bot]@users.noreply.github.com>
mr-danya
pushed a commit
to mr-danya/sentry-mcp
that referenced
this pull request
Oct 6, 2026
…missing env vars, new commands (#1461) ## Documentation Audit Report (2026-08-24) Weekly automated audit comparing the CLI implementation against its documentation. Changes since the last merged audit (PR getsentry#1400, 2026-08-11) include: the `sentry cli completion` command (getsentry#1427), sixel dashboard rendering (getsentry#1410), the `--environment` explore fix (#1442), and the 0.43.0 release. --- ## Findings & Fixes ### A. Undocumented or missing commands/subcommands | Command | Source | Expected doc location | Status | |---------|--------|----------------------|--------| | `sentry cli completion` | `src/commands/cli/completion.ts` (added in getsentry#1427) | `apps/cli-docs/src/fragments/commands/cli.md` | **Fixed** — added examples for bash, zsh, fish | All other commands in `src/commands/` have corresponding fragment files. Hidden backward-compat aliases (`send-event`, `send-envelope`, `bash-hook`, `whoami`, plural aliases) are correctly excluded from docs. ### B. Undocumented flags | Flag | Command | Source | Doc file | Status | |------|---------|--------|----------|--------| | `--sixel` / `-s` | `sentry dashboard view` | `src/commands/dashboard/view.ts` | `fragments/commands/dashboard.md` | **Fixed** — added example | All other non-hidden flags are auto-generated into the command docs via `generate-command-docs.ts`. ### C. Missing usage examples No new gaps. The `sentry cli completion` command was the only command without examples, now fixed. ### D. Stale descriptions | Command/Flag | Code brief | Doc description | Status | |-------------|-----------|-----------------|--------| | `sentry explore --environment` | Was: "Replay environment filter for --dataset replays" | Now works for all datasets (fixed in #1442) | **Fixed** — updated brief to "Environment filter" | ### E. Missing route mappings in skill generator **N/A** — `ROUTE_TO_REFERENCE` was removed and replaced with automatic 1:1 route-to-reference mapping via `groupRoutesByReference()` in `script/generate-skill.ts`. No manual mapping to go stale. ### F. Installation / distribution gaps No new gaps. Install script flags (`--no-modify-path`, `--no-completions`, `--no-agent-skills`) and env vars (`SENTRY_INSTALL_DIR`, `SENTRY_VERSION`, `SENTRY_INIT`) are documented in `getting-started.mdx`. Platform support table matches `.craft.yml` targets (macOS x64/arm64, Linux x64/arm64, Windows x64). ### G. Undocumented environment variables | Variable | Referenced in | Expected doc | Status | |----------|-------------|-------------|--------| | `DO_NOT_TRACK` | `src/lib/telemetry.ts` | `configuration.md` (generated from env-registry) | **Fixed** — added to env-registry.ts | | `SENTRY_PIPELINE` | `src/commands/build/upload.ts`, `src/lib/build/index.ts` | `configuration.md` | **Fixed** — added to env-registry.ts | Remaining niche/internal vars NOT added (intentionally excluded from user-facing docs): - `SENTRY_ENVIRONMENT` — bash-hook template only - `SENTRY_CLI_NO_EXIT_TRAP` — bash-hook template internal - `SENTRY_SCAN_DISABLE_WORKERS` — internal performance tuning - `SENTRY_CLI_INTEGRATION_TEST_VERSION_OVERRIDE` — test-only - `SENTRY_RN_*` — internal react-native wrapper vars - `SENTRY_TRACES_SAMPLE_RATE` — inherited from SDK, not a CLI config ### H. Auth / self-hosted gaps No new gaps. OAuth scopes in `self-hosted.md` and `DEVELOPMENT.md` are auto-generated (`GENERATED:START oauth-scopes`). The `--url` flag for `auth login` and `SENTRY_HOST`/`SENTRY_URL` behavior are documented. Token priority (OAuth > env token unless `SENTRY_FORCE_ENV_TOKEN`) is correct. ### I. Plugin/skills gaps No new gaps since the last audit. Skills install to `~/.claude` and `~/.agents` only. The `agentic-usage.md` correctly states this. Detection of other agents (Cursor, Windsurf, Copilot, etc.) is for telemetry and the docs correctly list them as "supported" agents (they can use the CLI, just not via auto-installed skills). ### J. README / DEVELOPMENT.md / contributing.md drift | File | Claim | Reality | Status | |------|-------|---------|--------| | `script/generate-docs-sections.ts` line 210 | "TypeScript types and Zod schemas" | Migrated to Valibot in getsentry#1389 (merged Aug 7) | **Fixed** | | `apps/cli-docs/src/content/docs/features.md` | DSN detection table lists 6 languages with specific `Sentry.init()` patterns | Scanner uses a universal DSN URL regex across 30+ file extensions | **Fixed** — updated table to match actual TEXT_EXTENSIONS set | Node.js version claims (v22.15+ for dev, >=20 for runtime) are correct. Build commands, test commands, and license (`FSL-1.1-Apache-2.0`) are all accurate. --- ## Top 5 Most Impactful Fixes (prioritized) 1. **DSN detection language table overhaul** (`features.md`) — The previous table implied language-specific `Sentry.init()` pattern matching, which is misleading. The universal regex approach supports 30+ file extensions. Users of Kotlin, Rust, Swift, Dart, C#, etc. would not have known their DSNs are detected. 2. **Missing `sentry cli completion` docs** (`cli.md` fragment) — New command from getsentry#1427 with no usage examples. Users discovering shell completions would miss this standalone alternative to `sentry cli setup`. 3. **Stale `--environment` flag brief** (`explore.ts`) — After #1442 fixed `--environment` to work for all datasets, the flag's `brief` string still said "Replay environment filter". Users would think it only applies to replays. 4. **Missing env vars in registry** (`env-registry.ts`) — `DO_NOT_TRACK` (industry-standard telemetry opt-out) and `SENTRY_PIPELINE` (build plugin identification) were referenced in code but absent from the generated configuration page. 5. **Zod→Valibot drift in project structure** (`generate-docs-sections.ts`) — The auto-generated project structure tree in `contributing.md` still said "Zod schemas" despite the migration to Valibot in getsentry#1389. Contributors would be confused about which validation library to use. <div><a href="https://cursor.com/agents/bc-2961de96-bee8-48d4-becb-d403a42a7cb6?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a> <a href="https://cursor.com/automations/8b0c0f35-da5e-409d-984c-5e39518ffb8a"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/view-automation-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/view-automation-light.png"><img alt="View Automation" width="141" height="28" src="https://cursor.com/assets/images/view-automation-dark.png"></picture></a> </div> --------- Co-authored-by: Cursor Agent <cursoragent@cursor.com> Co-authored-by: Miguel Betegón <miguelbetegongarcia@gmail.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: jared-outpost[bot] <jared-outpost[bot]@users.noreply.github.com>
mr-danya
pushed a commit
to mr-danya/sentry-mcp
that referenced
this pull request
Oct 6, 2026
…missing env vars, new commands (#1461) ## Documentation Audit Report (2026-08-24) Weekly automated audit comparing the CLI implementation against its documentation. Changes since the last merged audit (PR getsentry#1400, 2026-08-11) include: the `sentry cli completion` command (getsentry#1427), sixel dashboard rendering (getsentry#1410), the `--environment` explore fix (#1442), and the 0.43.0 release. --- ## Findings & Fixes ### A. Undocumented or missing commands/subcommands | Command | Source | Expected doc location | Status | |---------|--------|----------------------|--------| | `sentry cli completion` | `src/commands/cli/completion.ts` (added in getsentry#1427) | `apps/cli-docs/src/fragments/commands/cli.md` | **Fixed** — added examples for bash, zsh, fish | All other commands in `src/commands/` have corresponding fragment files. Hidden backward-compat aliases (`send-event`, `send-envelope`, `bash-hook`, `whoami`, plural aliases) are correctly excluded from docs. ### B. Undocumented flags | Flag | Command | Source | Doc file | Status | |------|---------|--------|----------|--------| | `--sixel` / `-s` | `sentry dashboard view` | `src/commands/dashboard/view.ts` | `fragments/commands/dashboard.md` | **Fixed** — added example | All other non-hidden flags are auto-generated into the command docs via `generate-command-docs.ts`. ### C. Missing usage examples No new gaps. The `sentry cli completion` command was the only command without examples, now fixed. ### D. Stale descriptions | Command/Flag | Code brief | Doc description | Status | |-------------|-----------|-----------------|--------| | `sentry explore --environment` | Was: "Replay environment filter for --dataset replays" | Now works for all datasets (fixed in #1442) | **Fixed** — updated brief to "Environment filter" | ### E. Missing route mappings in skill generator **N/A** — `ROUTE_TO_REFERENCE` was removed and replaced with automatic 1:1 route-to-reference mapping via `groupRoutesByReference()` in `script/generate-skill.ts`. No manual mapping to go stale. ### F. Installation / distribution gaps No new gaps. Install script flags (`--no-modify-path`, `--no-completions`, `--no-agent-skills`) and env vars (`SENTRY_INSTALL_DIR`, `SENTRY_VERSION`, `SENTRY_INIT`) are documented in `getting-started.mdx`. Platform support table matches `.craft.yml` targets (macOS x64/arm64, Linux x64/arm64, Windows x64). ### G. Undocumented environment variables | Variable | Referenced in | Expected doc | Status | |----------|-------------|-------------|--------| | `DO_NOT_TRACK` | `src/lib/telemetry.ts` | `configuration.md` (generated from env-registry) | **Fixed** — added to env-registry.ts | | `SENTRY_PIPELINE` | `src/commands/build/upload.ts`, `src/lib/build/index.ts` | `configuration.md` | **Fixed** — added to env-registry.ts | Remaining niche/internal vars NOT added (intentionally excluded from user-facing docs): - `SENTRY_ENVIRONMENT` — bash-hook template only - `SENTRY_CLI_NO_EXIT_TRAP` — bash-hook template internal - `SENTRY_SCAN_DISABLE_WORKERS` — internal performance tuning - `SENTRY_CLI_INTEGRATION_TEST_VERSION_OVERRIDE` — test-only - `SENTRY_RN_*` — internal react-native wrapper vars - `SENTRY_TRACES_SAMPLE_RATE` — inherited from SDK, not a CLI config ### H. Auth / self-hosted gaps No new gaps. OAuth scopes in `self-hosted.md` and `DEVELOPMENT.md` are auto-generated (`GENERATED:START oauth-scopes`). The `--url` flag for `auth login` and `SENTRY_HOST`/`SENTRY_URL` behavior are documented. Token priority (OAuth > env token unless `SENTRY_FORCE_ENV_TOKEN`) is correct. ### I. Plugin/skills gaps No new gaps since the last audit. Skills install to `~/.claude` and `~/.agents` only. The `agentic-usage.md` correctly states this. Detection of other agents (Cursor, Windsurf, Copilot, etc.) is for telemetry and the docs correctly list them as "supported" agents (they can use the CLI, just not via auto-installed skills). ### J. README / DEVELOPMENT.md / contributing.md drift | File | Claim | Reality | Status | |------|-------|---------|--------| | `script/generate-docs-sections.ts` line 210 | "TypeScript types and Zod schemas" | Migrated to Valibot in getsentry#1389 (merged Aug 7) | **Fixed** | | `apps/cli-docs/src/content/docs/features.md` | DSN detection table lists 6 languages with specific `Sentry.init()` patterns | Scanner uses a universal DSN URL regex across 30+ file extensions | **Fixed** — updated table to match actual TEXT_EXTENSIONS set | Node.js version claims (v22.15+ for dev, >=20 for runtime) are correct. Build commands, test commands, and license (`FSL-1.1-Apache-2.0`) are all accurate. --- ## Top 5 Most Impactful Fixes (prioritized) 1. **DSN detection language table overhaul** (`features.md`) — The previous table implied language-specific `Sentry.init()` pattern matching, which is misleading. The universal regex approach supports 30+ file extensions. Users of Kotlin, Rust, Swift, Dart, C#, etc. would not have known their DSNs are detected. 2. **Missing `sentry cli completion` docs** (`cli.md` fragment) — New command from getsentry#1427 with no usage examples. Users discovering shell completions would miss this standalone alternative to `sentry cli setup`. 3. **Stale `--environment` flag brief** (`explore.ts`) — After #1442 fixed `--environment` to work for all datasets, the flag's `brief` string still said "Replay environment filter". Users would think it only applies to replays. 4. **Missing env vars in registry** (`env-registry.ts`) — `DO_NOT_TRACK` (industry-standard telemetry opt-out) and `SENTRY_PIPELINE` (build plugin identification) were referenced in code but absent from the generated configuration page. 5. **Zod→Valibot drift in project structure** (`generate-docs-sections.ts`) — The auto-generated project structure tree in `contributing.md` still said "Zod schemas" despite the migration to Valibot in getsentry#1389. Contributors would be confused about which validation library to use. <div><a href="https://cursor.com/agents/bc-2961de96-bee8-48d4-becb-d403a42a7cb6?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a> <a href="https://cursor.com/automations/8b0c0f35-da5e-409d-984c-5e39518ffb8a"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/view-automation-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/view-automation-light.png"><img alt="View Automation" width="141" height="28" src="https://cursor.com/assets/images/view-automation-dark.png"></picture></a> </div> --------- Co-authored-by: Cursor Agent <cursoragent@cursor.com> Co-authored-by: Miguel Betegón <miguelbetegongarcia@gmail.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: jared-outpost[bot] <jared-outpost[bot]@users.noreply.github.com>
…oint Exposes Sentry's dedicated events-dropped endpoint to agents as a new find_dropped_events tool: ground-truth data-fidelity information (what Sentry received but dropped, and why) bucketed over time, alongside accepted volume so a caller can compute the dropped share. Surfaced directly (same tier as search_events) since an agent debugging a flat/spiky/low chart should be able to reach it without discovery. - api-client: getDroppedEvents() + DroppedEvents response schemas - tool: find_dropped_events (datasets: spans, logs, metrics) - registered in the catalog + direct surface; regenerated definitions Backed by an agent eval: naive agents given a user-phrased question reliably discovered and called this tool, and attributed flat/spiky charts to the right drop reason — where the same agents without it concluded "nothing is broken." Refs DAIN-1863
Remove doc comments that restated project framing / dev decisions rather than explaining non-obvious code. Matches the surrounding file convention, where sibling schemas, client methods, and tools carry no such comments. The caller-facing tool description and param descriptions are unchanged. Refs DAIN-1863
Three targeted edits to the tool description, keeping the tested structure: - Lead with what the tool captures (dropped before storage), not "received" — SDK-side drops (sample_rate, before_send) never reach Sentry. - Frame charts as one example of an accepted-only view, not the purpose; the tool's role is ground-truth data fidelity: is the data in Sentry or dropped. - Reframe the trust bullet around confirming data is actually in Sentry before relying on a query, aggregate, or dashboard. Regenerated tool/skill definitions. Refs DAIN-1863
Adding find_dropped_events to TOP_LEVEL_TOOL_NAMES changes the exact direct tool set these guardrail tests assert, so add it to DEFAULT_DIRECT_TOOL_NAMES. The catalog-search test queried 'event stacktrace' at limit 5; find_dropped_events now ranks there (its name contains 'events'), so raise the limit to 8 to keep asserting that catalog-only tools remain findable via search. Refs DAIN-1863
…d_dropped_events Mirrors two backend changes to the events-dropped endpoint: - errors dataset now maps to DataCategory.ERROR, so add it to the tool's dataset enum alongside spans/logs/metrics. - outcome (closed set of drop classifications) and reason (open sub-class) optionally scope the dropped side; accepted volume is always returned in full. getDroppedEvents forwards both filters; tool exposes them as optional params. Refs DAIN-1863
manessaraj
force-pushed
the
sarajmanes/dain-1863-mcp-dropped-events-tool
branch
from
October 6, 2026 20:19
143768d to
72d7acb
Compare
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a
find_dropped_eventstool that exposes Sentry's dedicated events-dropped endpoint to agents. It returns ground-truth data-fidelity information — what Sentry received but dropped (rate limited, over quota, filtered, invalid, abuse/spike protection, client-discarded viasample_rate/before_send, cardinality limited) — bucketed over time, plus the accepted volume per bucket so a caller can compute the dropped share.Refs DAIN-1863