> ## Documentation Index
> Fetch the complete documentation index at: https://docs.latitude.so/llms.txt
> Use this file to discover all available pages before exploring further.

# Openclaw

# OpenClaw telemetry

Stream OpenClaw agent runs into Latitude as traces. After setup, agent runs appear in your project's **Traces** view with model calls, tool calls, token usage, cost, timing, and nested subagent activity — as a proper `invoke_agent → chat → execute_tool` tree.

The recommended way is OpenClaw's **official OpenTelemetry exporter** (the bundled `@openclaw/diagnostics-otel` plugin), pointed at Latitude's OTLP ingest. It follows OpenTelemetry GenAI semantic conventions and is maintained by OpenClaw — see [OpenClaw's OpenTelemetry docs](https://docs.openclaw.ai/gateway/opentelemetry).

> **Note:** OpenClaw's official exporter is the preferred setup and is documented below. If you need to group a multi-turn conversation into a Latitude **session**, the Latitude-maintained [`@latitude-data/openclaw-telemetry`](https://github.com/latitude-dev/latitude-llm/tree/main/packages/telemetry/openclaw) plugin remains the only option that emits a session id today — the native exporter doesn't yet ([openclaw/openclaw#91927](https://github.com/openclaw/openclaw/issues/91927)).

## Prerequisites

* A [Latitude account](https://console.latitude.so/login) with a project
* OpenClaw 2026.6 or newer
* A Latitude **API key** and your **project slug** (project sidebar → **Settings → API Keys**)

## Setup

### 1. Install the exporter

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
openclaw plugins install clawhub:@openclaw/diagnostics-otel
```

### 2. Point it at Latitude

Add the `diagnostics.otel` block to `~/.openclaw/openclaw.json`. Latitude's ingest accepts OTLP/HTTP (protobuf) at `/v1/traces` and authenticates with your API key; the project is selected with the `X-Latitude-Project` header.

```jsonc theme={"theme":{"light":"github-light","dark":"github-dark"}}
{
  "diagnostics": {
    "otel": {
      "enabled": true,
      "traces": true,
      "protocol": "http/protobuf",
      "tracesEndpoint": "https://ingest.latitude.so/v1/traces",
      "headers": {
        "Authorization": "Bearer lat_xxx",
        "X-Latitude-Project": "your-project-slug"
      },
      "captureContent": {
        "enabled": true,
        "inputMessages": true,
        "outputMessages": true,
        "toolInputs": true,
        "toolOutputs": true,
        "systemPrompt": true
      }
    }
  }
}
```

The same keys can be set non-interactively:

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
openclaw config set 'diagnostics.otel.enabled' true
openclaw config set 'diagnostics.otel.traces' true
openclaw config set 'diagnostics.otel.protocol' '"http/protobuf"'
openclaw config set 'diagnostics.otel.tracesEndpoint' '"https://ingest.latitude.so/v1/traces"'
openclaw config set 'diagnostics.otel.headers' \
  '{"Authorization":"Bearer lat_xxx","X-Latitude-Project":"your-project-slug"}'
openclaw config set 'diagnostics.otel.captureContent' \
  '{"enabled":true,"inputMessages":true,"outputMessages":true,"toolInputs":true,"toolOutputs":true,"systemPrompt":true}'
```

### 3. Restart and verify

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
openclaw gateway restart
```

Send a message to an agent, then open your Latitude project and go to **Traces** — the run should appear within a few seconds.

## Structural-only telemetry

To capture trace structure (timing, model, token usage, cost, run/tool shape) without prompt, response, or tool content, set `captureContent.enabled` to `false`:

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
openclaw config set 'diagnostics.otel.captureContent.enabled' false
openclaw gateway restart
```

## Captured data and privacy

With `captureContent.enabled = true`, Latitude receives the content needed to reconstruct runs — prompts, responses, system instructions, and tool input/output — plus model metadata, token usage, and cost. The granular `captureContent.*` flags let you capture some kinds of content and not others. Content is **not** exported unless you opt in. Disable capture (or telemetry entirely) before working with sensitive material you don't want sent to Latitude.

## Disable

Pause the exporter without uninstalling:

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
openclaw config set 'diagnostics.otel.enabled' false
openclaw gateway restart
```

## Switching to the native exporter

If you previously installed `@latitude-data/openclaw-telemetry`, remove it and switch to the native exporter above:

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
openclaw plugins uninstall @latitude-data/openclaw-telemetry --force
openclaw plugins install clawhub:@openclaw/diagnostics-otel
# add the diagnostics.otel config from step 2, then:
openclaw gateway restart
```

The native exporter produces a cleaner `invoke_agent → chat → execute_tool` structure, and no changes are needed on the Latitude side.

> **Note — session grouping.** The native exporter does not export a session id (OpenClaw redacts session keys by design — see [OpenClaw's OpenTelemetry docs](https://docs.openclaw.ai/gateway/opentelemetry)), so each agent turn arrives as its own trace and the **Sessions** view won't group a multi-turn conversation. The `@latitude-data/openclaw-telemetry` plugin emits a `session.id` and does group turns. We're tracking opt-in upstream support in [openclaw/openclaw#91927](https://github.com/openclaw/openclaw/issues/91927); once it lands, Latitude groups automatically (we already resolve `session.id`, `gen_ai.session.id`, `gen_ai.conversation.id`, and `langfuse.session.id`).

## Troubleshooting

**No traces appear.** Restart the gateway, confirm the API key and project slug are correct, and send a new agent message. A `401`/`403` from ingest means the API key isn't valid for that project's organization.

**Traces show timing but no content.** `captureContent.enabled` is `false` — set it to `true` and restart.

**Traces aren't grouped into sessions.** Expected with the native exporter — it doesn't emit a session id (see the note above). Each turn is its own trace until [openclaw/openclaw#91927](https://github.com/openclaw/openclaw/issues/91927) ships an opt-in session attribute. For session grouping today, use the `@latitude-data/openclaw-telemetry` plugin.

**Traces silently never arrive.** Check that `tracesEndpoint` uses **`https://`**. Plain `http://` gets a `301` redirect that OTLP exporters don't follow on `POST`, so batches are dropped with no error.