Clawdbot has been exploding in usage over the past weeks, so we ran a hackday around it at LangWatch and quickly hit a familiar problem: great agent behavior, zero visibility into what was actually happening.

This weekend contributors from LangWatch, Orq, and Red Hat collaborated to add native OpenTelemetry instrumentation to OpenClaw, including support for the OTEL GenAI semantic conventions.

You can now trace agent execution steps, LLM calls, tool usage, and token-level costs in a standard OTEL pipeline instead of custom logging.

Setup guide: https://langwatch.ai/blog/instrumenting-your-openclaw-agent-...

+ PR here: https://github.com/openclaw/openclaw/pull/11100

Happy to answer questions about the approach and what’s coming next.

Solving a very real pain point here! It's also really helpful for understanding how to iterate and improve on the agents, instead of vibing the vibers' vibe.