Skip to main content

​
Overview

This guide shows you how to send traces from an agent built with Eve to Latitude. Eve is built on the Vercel AI SDK and exports standard OpenTelemetry spans (ai.streamText, ai.toolCall, …) through whatever exporter you register in agent/instrumentation.ts. Because Latitude already understands Vercel AI SDK spans, you can point Eve’s OTel exporter straight at Latitude’s OTLP endpoint — no Latitude SDK required.
You’ll keep building with Eve exactly as you do today. The exporter simply sends your traces to Latitude alongside any other observability backend.
The Eve integration is TypeScript only.

​
Requirements

  • A Latitude account and API key
  • A Latitude project slug
  • An Eve project (with an agent/instrumentation.ts file)

​
Steps

1

Install

npm install @vercel/otel @opentelemetry/exporter-trace-otlp-http
2

Point the exporter at Latitude

In agent/instrumentation.ts, register an OTLP exporter that targets Latitude’s ingestion endpoint. Eve auto-discovers this file and runs it at startup, which implicitly enables telemetry.
import { defineInstrumentation } from "eve/instrumentation"
import { registerOTel } from "@vercel/otel"
import { OTLPTraceExporter } from "@opentelemetry/exporter-trace-otlp-http"

export default defineInstrumentation({
  setup: ({ agentName }) =>
    registerOTel({
      serviceName: agentName,
      traceExporter: new OTLPTraceExporter({
        url: "https://ingest.latitude.so/v1/traces",
        headers: {
          Authorization: `Bearer ${process.env.LATITUDE_API_KEY!}`,
          "X-Latitude-Project": process.env.LATITUDE_PROJECT_SLUG!,
        },
      }),
    }),
})
Eve records full message history and model outputs on spans by default (recordInputs / recordOutputs). Set them to false for sensitive or regulated data.
3

Group turns into sessions (optional)

Eve tags every turn with eve.session.id, which Latitude reads automatically to group related traces into a session — no extra work needed.To also associate traces with an end user, return a user.id attribute from the step.started event so it lands on the spans:
export default defineInstrumentation({
  setup: ({ agentName }) => registerOTel({ /* … */ }),
  events: {
    "step.started"(input) {
      return {
        runtimeContext: {
          "user.id": input.channel.metadata.triggeringUserId ?? "",
        },
      }
    },
  },
})

​
Seeing Your Traces

Once connected, traces appear automatically in Latitude:
  1. Open your project in the Latitude dashboard
  2. Each turn shows input/output messages, model, token usage, latency, and errors
  3. Eve turns, model calls, and tool executions appear as nested spans, grouped by session