dsh-o11y-plugin

DeepSeek Harness ships built-in session-level OpenTelemetry telemetry but exposes no plugin-scoped metric or log pipeline to third-party plugins. The result is that every plugin wanting standard, consistent observability had to wire up its own providers, exporters, and configuration—a repetitive and error-prone task. dsh-o11y-plugin closes that gap in a single, drop-in step.

On startup the plugin registers global OpenTelemetry providers once. From that point on, any plugin that calls trace.getTracer(), metrics.getMeter(), or logs.getLogger() from @opentelemetry/api automatically exports traces, metrics, and logs through one consistently configured pipeline. It also bridges dsh session telemetry into the OTel log stream so platform-level and plugin-level data share a single timeline. Every knob—service name, OTLP/HTTP endpoint, per-signal toggles, metric export interval—is surfaced under the o11y namespace in the dsh Web settings UI for easy inspection and tuning.

It is built for dsh plugin authors who want community-compatible, standardized observability without re-implementing OTel plumbing per plugin. The plugin is stateless, writes no files, reads no credentials, and buffers telemetry in memory until the OTLP endpoint is reachable; if no collector answers, batches are dropped silently with no side effects. It is implemented on the official OpenTelemetry Node.js SDK, the same dependency family dsh uses for its own session telemetry, ensuring upstream and downstream compatibility out of the box.