npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@zotdotbot/openclaw-otel

v0.2.2

Published

Self-contained OpenTelemetry plugin for OpenClaw — connected traces, per-turn token/cost rollups, opt-in content capture, and metrics, emitted as GenAI-semconv OTLP to any backend. Ships as one bundled file with zero runtime dependencies.

Readme

@zotdotbot/openclaw-otel

npm version CI License: Apache 2.0

OpenTelemetry plugin for OpenClaw. One connected trace per agent turn, per-turn token/cost rollups, standard GenAI semconv — exported as OTLP to any backend (SigNoz, Datadog, Grafana, …). Ships as one bundled file with zero runtime dependencies.

openclaw.request [28.1s]                      ← one agent turn (any channel), one trace
├─ openclaw.agent.turn [27.3s]                ← gen_ai.usage.* rollup, agent.success
│  ├─ openclaw.context.assembled              ← prompt/system/message sizing, budget
│  ├─ chat claude-opus-4-6 [4.3s]             ← GenAI semconv CLIENT spans (+ ttfb, bytes)
│  ├─ openclaw.skill.used                     ← per-skill activation (name, source)
│  ├─ execute_tool exec [403ms]               ← per-call tool spans (+ exec exit_code)
│  ├─ openclaw.harness.run                    ← agentic-loop item counts
│  └─ chat claude-opus-4-6 [18.8s]
├─ openclaw.message.processed                 ← inbound outcome (top error source)
└─ openclaw.message.sent                      ← outbound reply (joins the trace)

Why

OpenClaw's built-in exporter scatters each turn across disconnected root spans — no session correlation, no per-turn token/cost rollup, no gen_ai.* semconv, so OTLP backends can't reconstruct what your agent actually did. This plugin is a drop-in replacement: strictly richer, correlated data, with none of the @opentelemetry/api global-singleton wrangling that breaks the DIY approach. Full story: docs/why.md.

Install

openclaw plugins install @zotdotbot/openclaw-otel

Flag-free on OpenClaw 2026.6.5+; older hosts may need an install flag or plain npm — see docs/compatibility.md. Then in openclaw.json:

{
  "plugins": {
    "entries": {
      "openclaw-otel": {
        "enabled": true,
        "hooks": { "allowConversationAccess": true },
        "config": {
          "endpoint": "http://localhost:4318",
          "serviceName": "my-agent"
        }
      }
    }
  }
}

Two things people miss: hooks.allowConversationAccess: true is required (per-plugin, not top-level) or conversation spans silently never appear, and something must be listening at endpoint or exports are silently dropped — see docs/configuration.md for backends, auth headers, content capture, and every config key.

Docs

| | | | --- | --- | | docs/why.md | The gaps in the built-in exporter, and how this plugin works | | docs/configuration.md | Every config key, backends/auth, content capture | | docs/compatibility.md | OpenClaw version support matrix | | CONTRACT.md | The frozen telemetry wire contract (spans, attributes, schema versioning) | | CONTRIBUTING.md | Dev setup, tests, and the contract-change rules | | SECURITY.md | Reporting vulnerabilities; content-capture trust boundary |

License

Apache-2.0 © 2026 Zot. See LICENSE and THIRD-PARTY-NOTICES.md.