← Back to list

dsh-otel

DeepSeek Harness Other Low risk

Exports the agent loop to GreptimeDB as OpenTelemetry traces, metrics and logs, with seven Grafana dashboards covering token usage, cost, session outcomes and per-turn latency.

把 agent loop 以 OpenTelemetry traces、metrics、logs 导出到 GreptimeDB,附七个 Grafana dashboard,覆盖 token 用量、成本、会话结果和每轮耗时。

How to install

DeepSeek Harness dsh plugin add @tma1-ai/dsh-plugin-greptimedb

About

@tma1-ai/dsh-plugin-greptimedb English | 中文 What a DeepSeek Harness run costs you in tokens, money, and time, written into GreptimeDB as OpenTelemetry traces, metrics, and logs. Seven Grafana dashboards read it back. No collector. No sidecar. No fork of DSH. It installs as an ordinary plugin, and every turn, model call, and tool execution becomes a row you can query: sql -- Slowest tool calls, with the model that requested them. SELECT span_name, model, duration_nano / 1000000 AS ms FROM ( SELECT span_name, duration_nano, MAX("span_attributes.gen_ai.request.model") OVER (PARTITION BY trace_id,…

Recommendation signals

53 Tool quality · Based on stars, downloads, maintenance, security and docs
– User interest · Adjusted by in-site views, install copies and download clicks
53 Overall
0views
0unique visitors
0install copies
0download clicks
0outbound clicks

Meta

License
Apache-2.0
Language
TypeScript
GitHub stars
9
mo. downloads
923
Last push
2026-09-03
Created
2026-08-25

Links

Basic safety check

Findings
None
Sources
curated:awesome-dsh-plugin.com, curated:awesome-dsh-plugin/awesome-dsh-plugin
Topics
deepseek, deepseek-harness, dsh, dsh-plugin, greptimedb, harness, observability, opentelemetry

Related plugins

DeepSeek Harness
Score73

TokenLedger

zh667/TokenLedger

Sidebar usage panel that attributes tokens to the relay site that served each request, read from your existing provider config: today/month/all-time totals, per-site and per-model breakdowns, a year activity heatmap, and New API / Sub2API / DeepSeek balances.

☆ 202 ↓ 1.4K Other ↗
DeepSeek Harness
Score71

dsh-context

bowenliang123/dsh-context

DSH context insight panel: Context dashboard + /context command + Context browser — one-stop context lifecycle management with categorized composition, content details, evolution trends, compaction/injection events, and stats.

☆ 1.5K ↓ 79.7K Other ↗
DeepSeek Harness
Score69

dsh-usage-statistics-panel

HaoyueQin/dsh-usage-statistics-panel

Usage statistics settings panel: 26-week activity heatmap, daily token trend with a cache hit-rate curve, per-model donut and breakdown, time-range filters, summary cards, one-time historical backfill and lossless rebuild.

☆ 9 ↓ 3.3K Other ↗
DeepSeek Harness
Score68

dsh-all-usage

ParticleLight/dsh-all-usage

Analyze usage across models, providers, workspaces, and time ranges — including custom start/end dates over the full retained history — with live cache-hit visibility and separate model and provider breakdowns. Includes hourly single-day trends, daily cross-day trends, a 53-week GitHub-style heatmap, usage streaks, model and workspace Token-share donut charts with Token, cost, and percentage details, independent combinable filters, cache-efficiency trends, DeepSeek account balance, workspace aliases, CSV export, and a durable ledger that preserves successfully flushed usage after session deletion — and after a workspace is deleted, where its recorded usage is summed into one Deleted row — and rebuilds incrementally — on restart, unchanged sessions are applied from the ledger without re-reading their logs (a per-session log revision is the change signal), and only changed/new events are folded. The workspace registry is kept fresh automatically through the DSH domain/changed probe: only added/removed workspaces are reprocessed incrementally, unchanged workspaces reuse their computed aggregates and ledger with zero rescan, and usage is strictly limited to DSH-registered workspaces (unregistered cwds are ignored). After a scan, lightweight revision status fetches full history only when the Host/data state changes and exposes non-sensitive sync health (revision reuse, rereads, ledger recovery, and failures). Token accounting is explicit: input is fresh (cache read/write and reasoning are separate buckets) and zero-usage replays never overwrite recorded usage. Chinese uses local time, English uses UTC; API access is loopback-only.

☆ 8 ↓ 2.8K Other ↗