Executive Summary
⚠️ Critical Infrastructure Gap: Unable to generate AIC consumption report due to missing telemetry backend access.
Both Sentry and Grafana MCP servers are unavailable in the workflow runtime environment. The workflow configuration declares these servers in imports (shared/mcp/sentry.md and shared/mcp/grafana.md), but they were not compiled into the final workflow manifest due to missing required secrets:
SENTRY_ACCESS_TOKEN (required for Sentry MCP server)
GRAFANA_URL and GRAFANA_SERVICE_ACCOUNT_TOKEN (required for Grafana MCP server)
Without access to these telemetry backends, no AIC consumption data can be queried or analyzed.
Key Metrics
| Metric |
Value |
| Events analyzed |
0 (no telemetry access) |
| Events with AIC data |
0 (no telemetry access) |
| Events with AIC data (Sentry) |
0 (no telemetry access) |
| Events with AIC data (Grafana) |
0 (no telemetry access) |
| Total AIC |
Unknown |
| Unique workflows |
Unknown |
| Avg AIC/event |
Unknown |
| P95 AIC/event |
Unknown |
Top 10 Workflows by AIC Consumption
No data available - telemetry backends are inaccessible.
Grafana AIC Findings
Status: Grafana MCP server not available in workflow runtime.
The workflow declares shared/mcp/grafana.md in its imports, which configures the Grafana MCP server with the following tools:
list_datasources
get_datasource
tempo_traceql-search
tempo_get-trace
tempo_get-attribute-names
tempo_get-attribute-values
tempo_docs-traceql
However, the compiled workflow manifest shows only github and safeoutputs MCP servers are active. The Grafana server was excluded from compilation due to missing secrets:
GRAFANA_URL
GRAFANA_SERVICE_ACCOUNT_TOKEN
Without these secrets configured in the repository, the Grafana MCP server cannot connect to the Tempo datasource, and therefore:
- No traces can be queried
- No AIC attributes can be verified
- No numeric aggregation of AIC values is possible
Data Quality and Gaps
Missing Infrastructure
Sentry MCP Server
- Status: Not available in workflow runtime
- Required Secret:
SENTRY_ACCESS_TOKEN
- Impact: Cannot query spans, transactions, or any telemetry events from Sentry
- Expected Tools:
whoami, find_organizations, find_projects, search_events, list_events, get_trace_details
Grafana MCP Server
- Status: Not available in workflow runtime
- Required Secrets:
GRAFANA_URL, GRAFANA_SERVICE_ACCOUNT_TOKEN
- Impact: Cannot query Tempo traces or verify AIC field presence
- Expected Tools:
list_datasources, tempo_traceql-search, tempo_get-trace, tempo_get-attribute-names
Compilation Evidence
The workflow's .lock.yml manifest (line 2) lists only two MCP servers:
"mcp_servers": [
{"name": "github", "tools": [...]},
{"name": "safeoutputs", "tools": [...]}
]
The sentry and grafana servers declared in the source markdown imports were not included in the compiled workflow, indicating missing required secrets at compilation time or runtime configuration issues.
Environment Verification
Runtime environment checks confirmed:
- No
SENTRY_ACCESS_TOKEN environment variable
- No
GRAFANA_URL or GRAFANA_SERVICE_ACCOUNT_TOKEN environment variables
- No
sentry or grafana CLI tools on PATH
- No MCP server connections established for Sentry or Grafana
OTLP Export Configuration
The workflow is correctly configured to export telemetry TO both backends:
GH_AW_OTLP_ENDPOINTS=[
{"url":"https://o205451.ingest.us.sentry.io/api/4511347087179777/integration/otlp","headers":"x-sentry-auth=..."},
{"url":"https://otlp-gateway-prod-eu-west-2.grafana.net/otlp","headers":"Authorization=..."}
]
This means spans ARE being sent to both Sentry and Grafana during workflow execution, but there is no read-path access to query that data back.
Recommendations
1. Configure Required Secrets (Critical)
Add the following repository secrets to enable telemetry queries:
For Sentry MCP Server:
SENTRY_ACCESS_TOKEN - Create a User Auth Token in Sentry with scopes: org:read, project:read, event:read, team:read
For Grafana MCP Server:
GRAFANA_URL - The base URL of the Grafana instance (e.g., https://your-org.grafana.net)
GRAFANA_SERVICE_ACCOUNT_TOKEN - A service account token with read access to Tempo datasources
Once these secrets are configured:
- Recompile the workflow:
gh aw compile .github/workflows/daily-token-consumption-report.md
- Verify the
.lock.yml manifest includes sentry and grafana in the mcp_servers array
- Commit and push the updated workflow
- Re-run this report
2. Verify Secret Scope
Ensure the secrets are available to scheduled workflows, not just workflow_dispatch or pull request events. Check repository settings > Secrets and variables > Actions.
3. Validate MCP Server Health
After secrets are configured, test MCP connectivity manually:
Sentry:
export SENTRY_ACCESS_TOKEN="<token>"
echo '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami"}}' | npx @sentry/mcp-server@0.33.0
Grafana:
export GRAFANA_URL="<url>"
export GRAFANA_SERVICE_ACCOUNT_TOKEN="<token>"
# Test via container
docker run --rm -e GRAFANA_URL -e GRAFANA_SERVICE_ACCOUNT_TOKEN \
grafana/mcp-grafana:1.1.0-alpine -t stdio --disable-write \
<<< '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_datasources"}}'
4. Alternative: Query Local Artifacts
As a temporary workaround until secrets are configured, consider querying workflow run logs or artifacts for AIC data:
- Parse OTLP export logs from the workflow's own execution
- Extract AIC values from agent output artifacts
- Use GitHub Actions API to retrieve workflow run metadata with cost estimates
This approach is limited to analyzing the current workflow's own consumption and cannot aggregate across all workflows in the repository.
References
Note: This report documents an observability infrastructure gap, not AIC consumption data. No telemetry queries were executed, and no AIC values were analyzed. Future reports will include actual consumption metrics once the required secrets are configured.
Generated by 📊 Daily AIC Consumption Report (Sentry + Grafana OTel) · goose · sonnet45 · 58.5 AIC · ⊞ 6.7K · ◷
Executive Summary
Both Sentry and Grafana MCP servers are unavailable in the workflow runtime environment. The workflow configuration declares these servers in imports (
shared/mcp/sentry.mdandshared/mcp/grafana.md), but they were not compiled into the final workflow manifest due to missing required secrets:SENTRY_ACCESS_TOKEN(required for Sentry MCP server)GRAFANA_URLandGRAFANA_SERVICE_ACCOUNT_TOKEN(required for Grafana MCP server)Without access to these telemetry backends, no AIC consumption data can be queried or analyzed.
Key Metrics
Top 10 Workflows by AIC Consumption
No data available - telemetry backends are inaccessible.
Grafana AIC Findings
Status: Grafana MCP server not available in workflow runtime.
The workflow declares
shared/mcp/grafana.mdin its imports, which configures the Grafana MCP server with the following tools:list_datasourcesget_datasourcetempo_traceql-searchtempo_get-tracetempo_get-attribute-namestempo_get-attribute-valuestempo_docs-traceqlHowever, the compiled workflow manifest shows only
githubandsafeoutputsMCP servers are active. The Grafana server was excluded from compilation due to missing secrets:GRAFANA_URLGRAFANA_SERVICE_ACCOUNT_TOKENWithout these secrets configured in the repository, the Grafana MCP server cannot connect to the Tempo datasource, and therefore:
Data Quality and Gaps
Missing Infrastructure
Sentry MCP Server
SENTRY_ACCESS_TOKENwhoami,find_organizations,find_projects,search_events,list_events,get_trace_detailsGrafana MCP Server
GRAFANA_URL,GRAFANA_SERVICE_ACCOUNT_TOKENlist_datasources,tempo_traceql-search,tempo_get-trace,tempo_get-attribute-namesCompilation Evidence
The workflow's
.lock.ymlmanifest (line 2) lists only two MCP servers:The
sentryandgrafanaservers declared in the source markdown imports were not included in the compiled workflow, indicating missing required secrets at compilation time or runtime configuration issues.Environment Verification
Runtime environment checks confirmed:
SENTRY_ACCESS_TOKENenvironment variableGRAFANA_URLorGRAFANA_SERVICE_ACCOUNT_TOKENenvironment variablessentryorgrafanaCLI tools on PATHOTLP Export Configuration
The workflow is correctly configured to export telemetry TO both backends:
This means spans ARE being sent to both Sentry and Grafana during workflow execution, but there is no read-path access to query that data back.
Recommendations
1. Configure Required Secrets (Critical)
Add the following repository secrets to enable telemetry queries:
For Sentry MCP Server:
SENTRY_ACCESS_TOKEN- Create a User Auth Token in Sentry with scopes:org:read,project:read,event:read,team:readFor Grafana MCP Server:
GRAFANA_URL- The base URL of the Grafana instance (e.g.,https://your-org.grafana.net)GRAFANA_SERVICE_ACCOUNT_TOKEN- A service account token with read access to Tempo datasourcesOnce these secrets are configured:
gh aw compile .github/workflows/daily-token-consumption-report.md.lock.ymlmanifest includessentryandgrafanain themcp_serversarray2. Verify Secret Scope
Ensure the secrets are available to scheduled workflows, not just
workflow_dispatchor pull request events. Check repository settings > Secrets and variables > Actions.3. Validate MCP Server Health
After secrets are configured, test MCP connectivity manually:
Sentry:
Grafana:
4. Alternative: Query Local Artifacts
As a temporary workaround until secrets are configured, consider querying workflow run logs or artifacts for AIC data:
This approach is limited to analyzing the current workflow's own consumption and cannot aggregate across all workflows in the repository.
References
Note: This report documents an observability infrastructure gap, not AIC consumption data. No telemetry queries were executed, and no AIC values were analyzed. Future reports will include actual consumption metrics once the required secrets are configured.