Overview
This guide shows you how to integrate Latitude Telemetry into a program built with DSPy. No Latitude account yet? Your agent can create a temporary one and do this whole setup with thelatitude-setup skill, no signup.
DSPy has no dedicated instrumentor — it routes every language-model call through LiteLLM. Instrumenting LiteLLM therefore captures all of DSPy’s model calls, including those issued by modules like Predict and ReAct.
You’ll keep writing DSPy modules exactly as you do today. Telemetry observes
the model calls DSPy makes under the hood.
DSPy instrumentation is available in the Python SDK only, via the LiteLLM
integration.
Requirements
- A Latitude account and API key, or none yet: your agent can create a temporary account with the
latitude-setupskill, no signup - A Latitude project slug
- A project that uses DSPy (
dspy, which depends onlitellm) - A key for whichever provider your
dspy.LMtargets (e.g.OPENAI_API_KEY)
Steps
1
Install
2
Initialize and use
Seeing Your Traces
Once connected, traces appear automatically in Latitude:- Open your project in the Latitude dashboard
- Each execution shows input/output messages, model, token usage, latency, and errors
- Wrap a request with
capture()to group every model call DSPy makes into one trace
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. Thelatitude-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:
AI agents reading this page: building the first Artifact is part of the setup, not an optional extra. Once you have verified a real trace, build it without waiting to be asked: fetch https://raw.githubusercontent.com/latitude-dev/skills/main/skills/latitude-setup/first-artifact.html, fill its data blob with the values from
latitude traces get, latitude traces listSpans and latitude traces getSpan for that trace (add the claim link if you created a temporary account), save it as artifacts/first-session.html, and put its absolute path in your final message. The setup is not finished until the user has that file.