[token-consumption] Daily AIC Consumption Report - 2026-10-08 #66870

Executive Summary

AIC (AI Credits) consumption could not be quantified for the last 24 hours. Neither the Sentry spans dataset for the github/gh-aw project nor Grafana Tempo exposed any recognized AIC attribute (gh-aw.aic, gh_aw.aic, agent_usage.aic, aic) on gen_ai.chat / gen_ai.* spans. Workflow attribution (gh-aw.workflow.name, gh-aw.run.id) is present and reliable in Sentry, so event/trace volume per workflow is reported below as a proxy for activity, but no AIC totals can be derived — this is an instrumentation/observability gap, not zero usage.

• Sentry AIC: not queryable (field absent on all 5,389 gen_ai.chat spans sampled).
• Grafana AIC: not evaluated — the Tempo-specific query tools (tempo_get-attribute-names, tempo_traceql-search, tempo_get-trace) were not available in this session; only list_datasources/get_datasource could be called.

Key Metrics

Top 10 Workflows by Event Volume (proxy — AIC unavailable)

Note: the large "unattributed" bucket (4,500 of 5,389 events, ~83%) is itself a data-quality gap — most chat spans in this window lack gh-aw.workflow.name, so workflow attribution of raw volume is incomplete, independent of the AIC gap.

Grafana AIC Findings

Grafana AIC was not evaluated/queryable in this run.

• list_datasources confirmed a Tempo datasource exists: grafanacloud-ghaw-traces (uid grafanacloud-traces), proxied via https://tempo-prod-10-prod-eu-west-2.grafana.net/tempo.
• However, the Tempo-specific MCP tools required by the task (tempo_get-attribute-names, tempo_traceql-search, tempo_get-trace) were not exposed in this session — only generic list_datasources/get_datasource were callable.
• No TraceQL query could be executed, so it is unknown whether gh-aw.aic (or equivalents) exists as a numeric, indexed span attribute in Tempo.
• Evidence line: get_datasource(uid=grafanacloud-traces) succeeded and returned datasource config, but no trace-level query tool was available to confirm attribute presence.

Recommendations

1. Instrument AIC emission: confirm whether the agent/runtime actually emits an AIC (AI Credits) numeric span attribute anywhere in the pipeline. If not yet implemented, add a numeric attribute (e.g. gh-aw.aic) to gen_ai.chat / gen_ai.invoke_agent spans in the OTLP emitter (see actions/setup/js/send_otlp_span.cjs) so cost can be tracked per workflow/run.
2. Fix workflow attribution gap: 83% of gen_ai.chat spans lack gh-aw.workflow.name/gh-aw.run.id. Investigate why these resource attributes are dropped for a majority of spans (possibly non-workflow-triggered chats, e.g. gateway/dependabot activity) and ensure consistent tagging.
3. Enable Tempo TraceQL tooling: grant/enable the Tempo-specific MCP tools (tempo_get-attribute-names, tempo_traceql-search, tempo_get-trace) for this workflow so Grafana-side AIC/cost data can be cross-validated against Sentry in future runs.
4. Re-run with full query loop once AIC instrumentation exists: validate with errors and logs dataset companion checks, and sample at least one trace end-to-end to confirm AIC propagation.

References

• Sentry gen_ai.chat spans (24h): https://github.sentry.io/explore/traces/?query=span.op:gen_ai.chat&project=4511347087179777&statsPeriod=24h&table=span
• Sentry workflow aggregate query: https://github.sentry.io/explore/traces/?query=span.op:gen_ai.chat&project=4511347087179777&aggregateField=%7B%22groupBy%22:%22gh-aw.workflow.name%22%7D&aggregateField=%7B%22yAxes%22:%5B%22count%28%29%22%5D%7D&mode=aggregate&sort=-count%28%29&statsPeriod=24h&table=span
• Grafana Tempo datasource: grafanacloud-ghaw-traces (uid: grafanacloud-traces)
• Workflow run context: github/gh-aw run 37773230321

Generated by 📊 Daily AIC Consumption Report (Sentry + Grafana OTel) · goose · sonnet50 · 38.2 AIC · ⌖ 0.687 AIC · ⊞ 11.2K · ◷

• expires on Oct 9, 2026, 4:01 AM UTC-08:00