Your cost dashboard can't tell you which agent ran up the bill
Drafted with AI help, human-reviewed by The Agent Loop. Short version: My own analytics dashboard said 52 views this morning while every per-post row printed null . The total was right, the attribution was broken, and the footnote even claimed the data didn't exist. That is what most agent cost tracking looks like: a correct number you can't decompose. A provider invoice tells you that spending…
The cost dashboard cannot provide information on which agent caused the bill. The dashboard shows a correct total cost but fails to break down the attribution, making it impossible to decompose the cost. A provider invoice indicates spending has risen but does not specify which agent or tool call raised it. OpenTelemetry's GenAI conventions lack a cost attribute in their published spec, and they mark token counters as a proxy for cost approximation.
However, spans that wrap tool calls do not carry usage fields, requiring manual price calculation for each span. This omission makes it difficult to accurately attribute costs at a per-tool level.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
