Observability for OpenClaw with Opik

OpenClaw can send trace data to Opik through the community plugin package @opik/opik-openclaw.

This integration captures:

• LLM spans (llm_input, llm_output)
• Tool spans (before_tool_call, after_tool_call)
• Agent-level run metadata (agent_end, usage/cost diagnostics)

Prerequisites

• OpenClaw version 2026.3.2 or newer.
• Opik project/workspace details (for cloud or enterprise deployments).

Setup

$
openclaw plugins install @opik/opik-openclaw

$
openclaw opik configure

$
openclaw opik status
$
openclaw gateway restart

Advanced configuration (manual JSON)

Use this only when you need explicit checked-in or templated plugin configuration. For the latest plugin-specific options, see opik-openclaw.

Add this to your OpenClaw config:

1
{
2
  "plugins": {
3
    "entries": {
4
      "opik": {
5
        "enabled": true,
6
        "config": {
7
          "enabled": true,
8
          "apiUrl": "https://www.comet.com/opik/api",
9
          "apiKey": "your-api-key",
10
          "projectName": "openclaw",
11
          "workspaceName": "default",
12
          "tags": ["openclaw"]
13
        }
14
      }
15
    }
16
  }
17
}

Environment variable fallbacks are also supported:

• OPIK_API_KEY
• OPIK_URL_OVERRIDE
• OPIK_PROJECT_NAME
• OPIK_WORKSPACE

Validate setup

$
openclaw opik status

Known limitation

Some OpenClaw embedded execution paths currently emit after_tool_call without a sessionKey. The plugin uses a best-effort fallback (single active trace or most recent active session), which can mis-correlate tool spans when multiple sessions run concurrently.

Next step

For OTEL-native pipelines, see OpenTelemetry integration.