No-Code

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 with plugin support enabled.
  • Opik project/workspace details (for cloud or enterprise deployments).

Install the plugin

$openclaw plugins install @opik/opik-openclaw
$openclaw plugins enable opik

Configure the plugin

Interactive setup

$openclaw opik configure

This command validates your Opik URL, validates API key access (when required), and writes plugin-scoped config.

Manual config

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

  1. Check plugin config:
$openclaw opik status
  1. Restart or run your OpenClaw gateway process.
  2. Send a message through OpenClaw.
  3. Verify traces appear in the configured Opik project.

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.