Skip to main content
Google ADK agents are instrumented by the OpenInference Google ADK instrumentor, which captures invocations, agent runs, model calls, and tool calls as OTLP spans. Point the exporter at AgentMark and the traces arrive normalized. Google ADK is a Python framework.

​
Setup

1

Install the instrumentor and the OTLP exporter

pip install openinference-instrumentation-google-adk \
  opentelemetry-sdk opentelemetry-exporter-otlp-proto-http
2

Point the exporter at AgentMark and instrument Google ADK

Use your AgentMark API key and app id from project settings.
from openinference.instrumentation.google_adk import GoogleADKInstrumentor
from opentelemetry.sdk.trace import TracerProvider
from opentelemetry.sdk.trace.export import BatchSpanProcessor
from opentelemetry.exporter.otlp.proto.http.trace_exporter import OTLPSpanExporter

provider = TracerProvider()
provider.add_span_processor(
    BatchSpanProcessor(
        OTLPSpanExporter(
            endpoint="https://api.agentmark.co/v1/traces",
            headers={
                "Authorization": "<YOUR_API_KEY>",  # raw key, no "Bearer" prefix
                "X-Agentmark-App-Id": "<YOUR_APP_ID>",
            },
        )
    )
)

GoogleADKInstrumentor().instrument(tracer_provider=provider)
3

Run your agent

Run your ADK agent as usual. Each invocation, agent run, model call, and tool call arrives in AgentMark as a span, grouped into a trace. See Traces and logs.

​
What AgentMark captures

Google ADK spans use the OpenInference attribute conventions — model, token usage, input and output messages, tool calls, settings, and span kind are all mapped onto AgentMark’s normalized trace fields, and token counts feed cost tracking. See OpenInference for the full attribute mapping.

​
Next steps

OpenInference

How AgentMark reads OpenInference attributes

Traces and logs

Explore traces once they arrive

​
Have questions?

Reach out any time: