[aw-failures] [P0] Sentry/Grafana MCP servers silently omitted when secrets missing — blocks Daily AIC Consumption Report

[github-actions]

Fix silent MCP-server omission — missing secrets should fail the compile/startup step loudly, not silently drop servers mid-run.

Affected workflow: Daily AIC Consumption Report (Sentry + Grafana OTel) (.github/workflows/daily-token-consumption-report.lock.yml)
Run analyzed: §31798707896 — failed 2026-08-14T12:03:14Z at "Parse agent logs for step summary", after the agent itself detected and self-reported the block mid-run.

Root cause

The workflow source correctly imports shared/mcp/sentry.md and shared/mcp/grafana.md, but the runtime .goose/mcp.json only registers github and safeoutputs. SENTRY_ACCESS_TOKEN, GRAFANA_URL, and GRAFANA_SERVICE_ACCOUNT_TOKEN are not configured as repo/org secrets, so the compiler/runtime silently excludes the Sentry and Grafana MCP servers instead of failing with an explicit error. Already diagnosed in detail by the agent's own self-filed issue #52709 (root cause, evidence, and remediation options fully written up there).

Proposed remediation

1. Add the three missing secrets (SENTRY_ACCESS_TOKEN, GRAFANA_URL, GRAFANA_SERVICE_ACCOUNT_TOKEN) at the repo or org level, or
2. Make MCP-server omission due to missing secrets a hard compile-time or startup error instead of a silent drop, so future misconfigurations fail fast instead of burning a full scheduled run before the agent notices.

Success criteria

Next scheduled run of Daily AIC Consumption Report completes with sentry and grafana present in .goose/mcp.json and successfully queries both, or fails at compile time with an explicit "missing secret" error instead of a silent MCP omission discovered mid-run.

Related to #52709 (self-filed diagnostic issue with full root-cause writeup), #52715

References:

• §31798707896
  Related to [aw-failures] [aw] Failure Investigator Report — 2026-08-13 19:10 UTC (6h) #52570

Generated by 🔍 [aw] Failure Investigator (6h) · agent · 151.5 AIC · ⌖ 46.8 AIC · ⊞ 5.3K · ◷

• expires on Aug 21, 2026, 5:23 AM UTC-08:00

[github-actions]

🍪 Issue Monster selected this for Copilot

I've identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent.

If assignment succeeds, the Copilot coding agent will analyze the issue and create a pull request with the fix.

Om nom nom! 🍪

🍪 Om nom nom by Issue Monster · gpt54 · 3.04 AIC · ⌖ 7.91 AIC · ⊞ 13.2K · ◷

[github-actions]

This issue was automatically closed because it expired on 2026-08-21T13:23:11.272Z.

Closed by Workflow