[deep-report] Fix Daily Token Consumption agent: Sentry token lacks org-level read permissions (6-day outage)

[github-actions]

Description

The daily-token-consumption workflow has failed to retrieve any telemetry for 6+ consecutive days (#30345). The root cause is identified: the Sentry token used by the workflow lacks organization-level read permissions, causing HTTP 403 errors. Additionally, the search_events span-query tool is absent from the mounted Sentry MCP server. The local OTel file (/tmp/gh-aw/otel.jsonl) only contains the setup span — no token-usage attributes are collected.

Expected Impact

• Restores daily token consumption visibility for all workflows
• Enables trending and cost analysis over time
• Surfaces per-workflow token efficiency for optimization

Fix Options

1. Token permission fix (preferred): Grant the Sentry token organization-level read permissions, or provision a new token with the correct scope
2. Alternative data source: If Sentry MCP is unavailable, fall back to OTel JSONL data collected during workflow runs (extend the harness to emit token-usage spans into /tmp/gh-aw/otel.jsonl)
3. MCP server update: Add search_events tool to the Sentry MCP server configuration

Current Behavior

• HTTP 403 on all Sentry queries
• search_events tool missing from MCP server
• Zero token data available for analysis

Suggested Agent

New: Sentry configuration agent, or manual infra fix

Estimated Effort

Quick (< 1 hour for token permission fix)

Data Source

DeepReport Intelligence Briefing — 2026-05-05 · Token Consumption Report issue #30345

Generated by DeepReport - Intelligence Gathering Agent · ● 369.8K · ◷

• expires on May 7, 2026, 3:34 PM UTC