Executive Summary

• Total AIC: Not queryable — no recognized AIC attribute (gh-aw.aic, gh_aw.aic, agent_usage.aic, aic) is indexed on spans in either backend for the report window (UTC 2026-10-16T00:00:00 – 2026-10-17T00:00:00).
• Sentry spans dataset returns gen_ai.chat and gen_ai.execute_tool spans (workflow activity is present and rich — tool calls, model names, durations), but attempting to select any AIC-related field (gh-aw.aic, gh_aw.aic, agent_usage.aic, aic, github.workflow, github.run_id) returns a hard validation error: Unknown attribute. This indicates these attributes are not registered/indexed in the current Sentry EAP schema for this project, not merely absent on individual spans.
• errors and logs datasets returned zero results for the window — confirmed empty, not a query failure.
• Grafana/Tempo: datasource discovered (grafanacloud-ghaw-traces, uid grafanacloud-traces), but no Tempo query tools (tempo_get-attribute-names, tempo_traceql-search, tempo_get-trace) were available in this session's toolset, so trace-level AIC confirmation in Grafana could not be performed this run.
• Net effect: workflow execution volume is clearly visible (gen_ai.chat / gen_ai.execute_tool spans across many traces/workflows within the window), but AIC cost attribution is currently an observability gap, not a zero-usage result.

Key Metrics

Top 10 Workflows by AIC Consumption

Not available — workflow attribution fields (github.workflow, gh_aw.workflow, transaction) were not returned alongside AIC data; AIC itself is unqueryable. Only generic tool/model span descriptions (e.g. chat copilot/gpt-5.4, chat claude-sonnet-5, execute_tool create_issue) were visible.

Grafana AIC Findings

AIC was not queryable in Grafana this run.

• Datasource confirmed: grafanacloud-ghaw-traces (tempo, uid grafanacloud-traces).
• Tempo query tools (tempo_get-attribute-names, tempo_traceql-search, tempo_get-trace) were not present in this session's available toolset, so attribute-level confirmation of gh-aw.aic/gh_aw.aic presence and type on Tempo spans could not be executed.
• Evidence: grafana__get_datasource(uid: grafanacloud-traces) succeeded and returned valid Tempo connection config, confirming the backend itself is reachable — the gap is tool availability for trace querying, not datasource misconfiguration.

Recommendations

1. Instrument AIC as a numeric span attribute: confirm the OTLP exporter (see actions/setup/js/send_otlp_span.cjs) actually emits gh-aw.aic (or an agreed canonical name) as a numeric attribute on gen_ai.chat/gen_ai.execute_tool spans, and that the attribute is registered in the Sentry EAP schema for this project so it becomes a selectable/queryable field.
2. Add workflow attribution fields: ensure gh-aw.workflow.name (or equivalent) is emitted and indexed so AIC can be grouped and ranked by workflow once queryable.
3. Enable Tempo trace-query tooling for future runs (or grant this workflow access to tempo_get-attribute-names/tempo_traceql-search) so Grafana-side AIC confirmation can act as a cross-check against Sentry.
4. Re-run field discovery with a minimal, schema-valid field set (e.g. id, span.op, timestamp only) plus incremental attribute probing to determine the full list of currently indexed custom attributes, to avoid blind guesses at attribute names going forward.

References

• Sentry spans explore (gen_ai.chat/gen_ai.execute_tool, 24h): https://github.sentry.io/explore/traces/?query=span.op:gen_ai*&project=4511347087179777&statsPeriod=24h&table=span
• Sentry errors explore (24h, empty): https://github.sentry.io/explore/discover/homepage/?dataset=errors&queryDataset=error-events&project=4511347087179777&statsPeriod=24h
• Sentry logs explore (24h, empty): https://github.sentry.io/explore/logs/?project=4511347087179777&statsPeriod=24h
• Grafana Tempo datasource: grafanacloud-ghaw-traces (uid: grafanacloud-traces)

Generated by 📊 Daily AIC Consumption Report (Sentry + Grafana OTel) · goose · sonnet50 · 30.4 AIC · ⌖ 0.771 AIC · ⊞ 12.8K · ◷

• expires on Oct 18, 2026, 2:40 AM UTC-08:00