Open-Source Observability · comet-ml

opik-openclaw

Opik-OpenClaw is an official observability plugin that captures detailed traces of OpenClaw agent runs, including LLM calls, tool invocations, and sub-agent activity. It exports these traces to Opik (Comet ML's open-source tracing platform) for monitoring, debugging, and cost tracking.

Talk to DEV.co Discuss Implementation

Source: GitHub — github.com/comet-ml/opik-openclaw

651

GitHub stars

Forks

TypeScript

Primary language

Apache-2.0

License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

Field	Value
Repository	comet-ml/opik-openclaw
Owner	comet-ml
Primary language	TypeScript
License	Apache-2.0 — OSI-approved
Stars	651
Forks	75
Open issues	14
Latest release	v0.2.17 (2026-05-22)
Last updated	2026-07-06
Source	https://github.com/comet-ml/opik-openclaw

What opik-openclaw is

TypeScript plugin that hooks into OpenClaw's event system (llm_input, llm_output, tool_call, subagent lifecycle) and exports structured traces to Opik via REST API. Runs inside the OpenClaw Gateway process and supports local or cloud-hosted Opik backends with configurable retry logic, trace cleanup, and transcript sanitization.

Quickstart

Get the opik-openclaw source

Clone the repository and explore it locally.

terminalbash

1git clone https://github.com/comet-ml/opik-openclaw.git2cd opik-openclaw3# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Multi-agent observability and cost tracking

Monitor LLM token usage, API costs, and latency across OpenClaw agent runs with native integration. Correlate parent-agent and sub-agent traces for end-to-end visibility.

Production debugging of agent failures

Capture complete request/response sequences, tool call inputs/outputs, and error states in Opik for rapid root-cause analysis without post-hoc log parsing.

Agent evaluation and optimization workflows

Export agent traces to Opik's evaluation platform to systematically test, score, and iterate on agent behavior and tool selection.

Implementation considerations

Requires explicit `allowConversationAccess: true` hook permission in OpenClaw config to access LLM prompts/responses; document security implications with ops team.
Plugin traces are flushed asynchronously; configure `staleTraceTimeoutMs` and `staleSweepIntervalMs` to balance memory usage and trace completeness in high-volume scenarios.
API key must be provisioned in Opik beforehand; use environment fallbacks (`OPIK_API_KEY`, `OPIK_URL_OVERRIDE`, etc.) for CI/CD and avoid hardcoding credentials.
Node.js ≥22.12.0 and npm ≥10 required; confirm gateway host dependencies before install.
Tool result transcript sanitization (`toolResultPersistSanitizeEnabled`) is disabled by default; enable explicitly if local image refs need rewriting for external persistence.

When to avoid it — and what to weigh

OpenClaw version < 2026.3.2 — Plugin requires OpenClaw ≥2026.3.2. Older versions lack necessary hook APIs; verify your OpenClaw version before deployment.
No observability backend needed — If your use case requires only real-time local debugging without centralized trace storage or retrospective analysis, the plugin adds unnecessary overhead.
Air-gapped or offline environments — Plugin requires outbound HTTPS connectivity to Opik API. Confirm network policies permit calls to Opik endpoint (default: https://www.comet.com/opik/api) before deployment.
Single-threaded or low-latency requirements — Plugin runs in the gateway process and may introduce latency due to trace flush retries. Not suitable for ultra-low-latency gating if trace writes block agent responses.

License & commercial use

Apache License 2.0 (Apache-2.0). Permissive OSI-approved license permitting commercial use, distribution, and modification with Apache 2.0 conditions (notice retention, disclaimer of warranty).

Apache-2.0 permits commercial use without royalties. However, this is a plugin for OpenClaw (whose license status requires separate review) and Opik (Comet ML's observability platform, with separate commercial terms). Verify OpenClaw and Opik commercial licensing independently; plugin licensing alone does not guarantee end-to-end commercial clearance.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

Signal	Assessment
Maintenance	Active
Documentation	Adequate
License clarity	Clear
Deployment complexity	Low
DEV.co fit	Strong
Assessment confidence	High

Security considerations

Plugin must access LLM prompts, tool inputs, and agent metadata to trace behavior; requires explicit `allowConversationAccess` permission. API key exposure risk via env vars or config files; use secure secret management (e.g., sealed secrets, HashiCorp Vault). Plugin runs inside gateway process; no isolation. Outbound HTTPS to Opik endpoint required; validate certificate and network policies. Local image refs in tool results can be sanitized before persistence if enabled.

Alternatives to consider

Opik Python/JavaScript SDK (direct integration)

If you control agent code, you can instrument directly with Opik SDK without a plugin. Offers finer-grained control but requires code changes and is not OpenClaw-specific.

LangSmith or Arize LLM observability

Alternative closed/proprietary platforms for agent tracing and evaluation. May have different pricing, feature sets, and integration pathways; evaluate based on your LLM stack and observability requirements.

Custom logging/tracing pipeline (e.g., OpenTelemetry + Jaeger)

Roll-your-own observability using standard instrumentation and open backends. Higher operational overhead but no vendor lock-in; suitable if you already have observability infrastructure.

Software development agency

Build on opik-openclaw with DEV.co software developers

Install the Opik-OpenClaw plugin to start capturing traces, monitoring costs, and debugging agent behavior. Requires OpenClaw ≥2026.3.2 and Opik account (cloud or self-hosted).

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

opik crabwalk fastapi-observability

Related on DEV.co

Explore the category and the services that help you build with it.

Open-Source Observability AI Development API Development DevOps Talk to DEV.co

opik-openclaw FAQ

Do I need a separate Opik account or can I self-host Opik?

Plugin supports both Opik Cloud (SaaS, free tier available) and self-hosted Opik. Configure endpoint and credentials during setup wizard; use `apiUrl` config or `OPIK_URL_OVERRIDE` env var to point to self-hosted instance.

What happens if the Opik backend is unreachable?

Plugin implements configurable retry logic (`flushRetryCount`, `flushRetryBaseDelayMs`) and stale trace cleanup. If Opik is down, traces are held in memory and flushed on reconnection; see config options to tune behavior.

Does the plugin slow down my OpenClaw agents?

Plugin runs async trace flushes; latency depends on Opik API responsiveness and network conditions. For ultra-low-latency requirements, benchmark with your Opik backend and tune flush retry/timeout settings.

Can I use the plugin with multiple OpenClaw gateways?

Yes. Install plugin on each gateway independently and configure each to point to the same Opik project/workspace. Traces from all gateways will be centralized in Opik.

Custom software development services

Adopting opik-openclaw is usually one piece of a larger software development effort. As a software development agency, DEV.co provides software development services and web development expertise — pairing senior software developers and web developers with your team to design, build, and operate open-source observability software in production.

Ready to instrument your OpenClaw agents?

Install the Opik-OpenClaw plugin to start capturing traces, monitoring costs, and debugging agent behavior. Requires OpenClaw ≥2026.3.2 and Opik account (cloud or self-hosted).

Talk to DEV.co Schedule a Consultation