[Bug]: AgentOps does not aggregate Google ADK Gemini token usage because ADK emits gen_ai.usage.input_tokens/output_tokens but AgentOps expects prompt_tokens/completion_tokens

[KalidasKalimuthu]

Contact Details

k.kalidas@gmail.com

📦 Package Version

0.4.21

🎞️ Framework Version

google adk

🔎 Describe the Bug

AgentOps captures ADK Gemini LLM spans and latency correctly, but trace metrics show zero tokens and zero cost. The issue appears to be a token attribute naming mismatch. Google ADK emits token usage as gen_ai.usage.input_tokens and gen_ai.usage.output_tokens, while AgentOps appears to aggregate only gen_ai.usage.prompt_tokens, gen_ai.usage.completion_tokens, and gen_ai.usage.total_tokens. The ADK trace contains valid Gemini usage_metadata and non-zero token attributes, but AgentOps metrics ignore them.

Details:
Agent Framework: google-adk (Version: 2.1.0)
LLM : gemini-2.5-flash-lite
agentops (0.4.21)
Programming Language : Python 3.13

In AgentOps SpanAttributes, token usage constants are defined as:
LLM_USAGE_COMPLETION_TOKENS = "gen_ai.usage.completion_tokens"
LLM_USAGE_PROMPT_TOKENS = "gen_ai.usage.prompt_tokens"
LLM_USAGE_TOTAL_TOKENS = "gen_ai.usage.total_tokens"

But ADK emits:
gen_ai.usage.input_tokens
gen_ai.usage.output_tokens

This creates a mismatch:

ADK emits → gen_ai.usage.input_tokens
AgentOps expects → gen_ai.usage.prompt_tokens
ADK emits → gen_ai.usage.output_tokens
AgentOps expects → gen_ai.usage.completion_tokens

This appears to be why AgentOps trace metrics return zero tokens/cost

Please normalize input_tokens → prompt_tokens, output_tokens → completion_tokens, and compute total_tokens when absent.

adk single invocation.json

🤝 Contribution

• Yes, I'd be happy to submit a pull request with these changes.
• I need some guidance on how to contribute.
• I'd prefer the AgentOps team to handle this update.

[KalidasKalimuthu]

Additional information: Json of events.
{
"modelVersion": "gemini-2.5-flash-lite",
"content": {
"parts": [
{
"functionCall": {
"id": "adk-fefe5e34-ae79-4b10-8300-72fb4515e126",
"args": {
"customer_id": "CUST001"
},
"name": "get_purchase_history"
}
}
],
"role": "model"
},
"finishReason": "STOP",
"usageMetadata": {
"candidatesTokenCount": 13,
"candidatesTokensDetails": [
{
"modality": "TEXT",
"tokenCount": 13
}
],
"promptTokenCount": 425,
"promptTokensDetails": [
{
"modality": "TEXT",
"tokenCount": 425
}
],
"totalTokenCount": 438,
"trafficType": "ON_DEMAND"
},
"avgLogprobs": -0.0007881865335198549,
"invocationId": "e-ca5a9a48-9c52-42a8-bf0e-4fcc96b025b4",
"author": "customer_service_agent",
"actions": {},
"nodeInfo": {
"path": "customer_service_agent@1"
},
"longRunningToolIds": [],
"id": "0e9f68e3-2000-46e8-90e5-a14a2f127130",
"timestamp": 1783004104.5057309
}

[KalidasKalimuthu]

Also getting this message during init.
🖇 AgentOps: Could not wrap google.adk.telemetry.trace_tool_response: module 'google.adk.telemetry' has no attribute 'trace_tool_response'
🖇 AgentOps: Google ADK patching complete
🖇 AgentOps: Google ADK instrumentation enabled