Skip to main content
Using an agent? Install the Latitude skills and let it handle the setup below. latitude-setup instruments your app or agent harness, verifies traces arrive, creates a temporary account if you don’t have one yet (no signup), and ends by building your first Artifact.

Overview

This guide shows you how to integrate Latitude Telemetry into an application that uses the Google Agent Development Kit (ADK) (google-adk for Python). No Latitude account yet? Your agent can create a temporary one and do this whole setup with the latitude-setup skill, no signup. Latitude includes dedicated instrumentation for Google ADK, so agent runs, model generations, and tool calls appear as traces.
You’ll keep calling Google ADK exactly as you do today. Telemetry observes agent runs, model calls, and tool calls as they happen.
Google ADK instrumentation is available in the Python SDK only.

Requirements

  • A Latitude account and API key, or none yet: your agent can create a temporary account with the latitude-setup skill, no signup
  • A Latitude project slug
  • A project that uses Google ADK (google-adk)
  • A Gemini API key (set as GOOGLE_API_KEY)

Steps

1

Install

2

Initialize and use


What you get

Each agent run shows up as a trace with nested spans:
  • Agent spans — agent name, instructions, and configured tools
  • Generation spans — model, input/output messages, and token usage
  • Tool spans — tool calls with input arguments and output
Wrap a request or job with capture() to attach a user_id, session_id, tags, or metadata to every span produced inside.

Seeing Your Traces

Once connected, traces appear automatically in Latitude:
  1. Open your project in the Latitude dashboard
  2. Each agent run shows the full hierarchy of agent → generation → tool calls
  3. Token usage and latency are aggregated at every level

See what was captured

Once a real run has landed, your agent builds your first Artifact: a single HTML page, in the Latitude look, with everything the telemetry captured from that session: model calls, tool calls, tokens, cost, timing, and the conversation as the model saw it. It is the fastest way to check the integration end to end and to see what Latitude will have to work with. The latitude-setup skill does this as its last step from its bundled first-artifact.html template, filling the page with the values the latitude CLI returns for the trace, and adds a Claim your workspace button when the account is temporary. If you set things up by hand, the same template and instructions live in the skills repo. Prompt, if you need to ask for it: