Telemetry Overview

Latitude Telemetry instruments your AI application and sends traces to Latitude. Built entirely on OpenTelemetry, it works alongside your existing observability stack (Datadog, Sentry, Jaeger, etc.) without conflicts or vendor lock-in. Once connected, every LLM execution becomes a trace in Latitude that you can inspect in the Traces view, enrich with scores and annotations, and evaluate with Evaluations.

Agentic installation

The fastest way to add Latitude is to let your coding agent (Claude Code, Cursor, Windsurf, etc.) install it for you. The Latitude skill guides the agent through codebase discovery (existing OpenTelemetry, conflicting LLM-observability vendors, which LLM SDKs are in use, where LLM calls actually happen), picks the right install path, places initialization correctly, and verifies that traces land in your project.

Fastest path: skill + MCP together. Install the Latitude MCP server in your agent alongside the telemetry skill. The MCP lets the agent create the Latitude project and look up your API key directly; the skill then wires tracing into your codebase. Together they finish the install without you leaving the editor.

Ask your coding agent

Paste this prompt into your agent:

Install the Latitude AI skill from github.com/latitude-dev/skills and use
it to add tracing to this application with Latitude following best practices.

The agent will fetch the skill, read your codebase, ask only the questions it can’t answer from the code, and produce a working install.

Install the skill manually

If you prefer to install the skill ahead of time (no global setup needed — npx runs it directly):

npx skills add latitude-dev/skills --skill "latitude-telemetry"

Then in your agent:

Add tracing to this application with Latitude following best practices.

The skill covers TypeScript and Python, the providers and frameworks listed in Supported Integrations, and audits existing OpenTelemetry setups for compatibility.

Manual installation

One SDK bootstrap class sets up everything: auto-instrumentation, the Latitude exporter, and async context propagation:

TypeScript
Python

npm install @latitude-data/telemetry

import { Latitude } from "@latitude-data/telemetry"
import OpenAI from "openai"

const latitude = new Latitude({
  apiKey: process.env.LATITUDE_API_KEY!,
  project: process.env.LATITUDE_PROJECT_SLUG!,
  instrumentations: { openai: OpenAI },
})

await latitude.ready

const openai = new OpenAI()
const response = await openai.chat.completions.create({
  model: "gpt-4o",
  messages: [{ role: "user", content: "Hello" }],
})

await latitude.shutdown()

pip install latitude-telemetry

import openai
from openai import OpenAI

from latitude_telemetry import Latitude

latitude = Latitude(
    api_key="your-api-key",
    project="your-project-slug",
    instrumentations={"openai": openai},
)

client = OpenAI()
response = client.chat.completions.create(
    model="gpt-4o",
    messages=[{"role": "user", "content": "Hello"}],
)

latitude.shutdown()

That’s it. Your LLM calls now appear as traces in Latitude.

Tracing several agents into separate Latitude projects from one process? You don’t need a separate SDK instance per project. Skip the constructor project and pass project on each capture() instead — spans route to whichever project the active capture declares. See Project scoping for the full pattern, the precedence rules, and the bare-OpenTelemetry alternative.

Adding Context with `capture()`

Auto-instrumentation traces LLM calls without any extra code. Use capture() when you want to attach business context such as user IDs, session IDs, tags, or metadata to group and filter traces in Latitude.

TypeScript
Python

import { Latitude, capture } from "@latitude-data/telemetry"
import OpenAI from "openai"

const latitude = new Latitude({
  apiKey: process.env.LATITUDE_API_KEY!,
  project: process.env.LATITUDE_PROJECT_SLUG!,
  instrumentations: { openai: OpenAI },
})

await latitude.ready

await capture(
  "handle-user-request",
  async () => {
    const response = await openai.chat.completions.create({
      model: "gpt-4o",
      messages: [{ role: "user", content: userMessage }],
    })
    return response.choices[0].message.content
  },
  {
    userId: "user_123",
    sessionId: "session_abc",
    tags: ["production", "v2-agent"],
    metadata: { requestId: "req-xyz" },
  },
)

await latitude.shutdown()

import openai

from latitude_telemetry import Latitude, capture

latitude = Latitude(
    api_key="your-api-key",
    project="your-project-slug",
    instrumentations={"openai": openai},
)

capture(
    "handle-user-request",
    lambda: client.chat.completions.create(
        model="gpt-4o",
        messages=[{"role": "user", "content": user_message}],
    ),
    {
        "user_id": "user_123",
        "session_id": "session_abc",
        "tags": ["production", "v2-agent"],
        "metadata": {"request_id": "req-xyz"},
    },
)

latitude.shutdown()

capture() does not create spans. It only attaches context to spans created by auto-instrumentation. Wrap the request or agent entrypoint once; you don’t need to wrap every internal step.

Streaming

When streaming responses, consume the stream inside the capture() callback so the span duration covers the full operation and child spans nest correctly:

TypeScript
Python

await capture("stream-reply", async () => {
  const stream = await openai.chat.completions.create({
    model: "gpt-4o",
    messages: [{ role: "user", content: input }],
    stream: true,
  })

  for await (const chunk of stream) {
    const content = chunk.choices[0]?.delta?.content
    if (content) res.write(content)
  }
  res.end()
})

def stream_reply():
    stream = client.chat.completions.create(
        model="gpt-4o",
        messages=[{"role": "user", "content": input}],
        stream=True,
    )
    for chunk in stream:
        if chunk.choices[0].delta.content:
            yield chunk.choices[0].delta.content

capture("stream-reply", stream_reply)

How It Fits Into Your Stack

Latitude Telemetry is built on OpenTelemetry standards:

Auto-instrumentation patches your LLM SDK (OpenAI, Anthropic, etc.) to emit spans for every call.
LatitudeSpanProcessor filters for LLM-relevant spans (gen_ai.*, ai.*, openinference.* attributes) and exports them to Latitude via OTLP.
capture() uses OpenTelemetry’s native context.with() to attach Latitude-specific attributes (user, session, tags) to spans within its scope.

If you already run Sentry or another OpenTelemetry-compatible SDK, initialize it first and construct Latitude second so Latitude can attach to the existing provider when possible. You can also add LatitudeSpanProcessor explicitly alongside existing processors. See the TypeScript SDK or Python SDK reference for advanced setup.

Supported Integrations

Providers

Provider	Instrumentation	Package (TS)	Package (Python)
OpenAI	`"openai"`	`openai`	`openai`
Anthropic	`"anthropic"`	`@anthropic-ai/sdk`	`anthropic`
Amazon Bedrock	`"bedrock"`	`@aws-sdk/client-bedrock-runtime`	`boto3`
Cohere	`"cohere"`	`cohere-ai`	`cohere`
Together AI	`"togetherai"`	`together-ai`	`together`
Vertex AI	`"vertexai"`	`@google-cloud/vertexai`	`google-cloud-aiplatform`
Google AI Platform	`"aiplatform"`	`@google-cloud/aiplatform`	`google-cloud-aiplatform`
Azure OpenAI	`"openai"`	`openai`	`openai`

Frameworks

Framework	Instrumentation	Package (TS)	Package (Python)
Vercel AI SDK	-	`ai`	-
OpenAI Agents SDK	`"openai-agents"`	`@openai/agents`	`openai-agents`
LangChain	`"langchain"`	`langchain`	`langchain-core`
LlamaIndex	`"llamaindex"`	`llamaindex`	`llama-index`
Mastra	-	`@mastra/core`	-

Next Steps

SDK Reference: TypeScript SDK · Python SDK
Other languages: OTLP Exporter — connect from Go, Java, Ruby, .NET, or any OpenTelemetry-supported language
Understand your data: Traces · Sessions
Act on your data: Evaluations · Annotations

Getting Started

Telemetry

Observability

Search

Evaluations

Annotations

Scores

Issues

Simulations

Agentic installation

Ask your coding agent

Install the skill manually

Manual installation

Adding Context with `capture()`

Streaming

How It Fits Into Your Stack

Supported Integrations

Providers

Frameworks

Next Steps

Getting Started

Telemetry

Observability

Search

Evaluations

Annotations

Scores

Issues

Simulations

Documentation Index

​Agentic installation

​Ask your coding agent

​Install the skill manually

​Manual installation

​Adding Context with capture()

​Streaming

​How It Fits Into Your Stack

​Supported Integrations

​Providers

​Frameworks

​Next Steps

Agentic installation

Ask your coding agent

Install the skill manually

Manual installation

Adding Context with `capture()`

Streaming

How It Fits Into Your Stack

Supported Integrations

Providers

Frameworks

Next Steps