简介
接收 OTLP 链路、指标与日志，查看 span 瀑布图，并通过 DBX 内置 DuckDB 用 SQL 分析。
权限
1 项权限
权限代码在安装时授予，此处按 manifest 原文展示。
版本历史
- v0.2.22026年9月24日最新
UI copy only — no behaviour change. - The workbench heading read "OpenTelemetry 浏览器". Contributors read that as a web browser and looked for an outbound browsing/fetching feature, which the plugin deliberately does not have: it only listens. The heading is now "OpenTelemetry 遥测"; the English heading was already just "OpenTelemetry".
- v0.2.12026年9月24日
Bugfix release: the workbench status card now reports the telemetry actually stored on disk. - The sidecar's per-process counters reset to zero on every restart, so the status card showed 0 spans / 0 metrics / 0 logs next to a data dir full of files and "Start receiver" looked like it had done nothing. Counts are now initialized from a recount of the persisted JSONL files. - Retention purge recomputes the affected signal counters from disk (including files written by a previous run) instead of leaving stale totals, and closes only the purged day's writer instead of every open writer of that signal. - Regression tests cover the restart recount, purge recount and the surviving current-day writer; the plugin was verified end-to-end against a real data directory (old build reported zeros, 0.2.1 reports the true persisted numbers) plus the smoke (21 checks) and end-to-end OTLP SDK suites (13 checks).
- v0.2.02026年9月23日
Initial DBX Store submission. - OTLP/HTTP receiver (/v1/traces, /v1/metrics, /v1/logs) accepting application/x-protobuf and application/json, plus OTLP/gRPC on 4317 (set grpc_port to 0 for HTTP-only). - Telemetry is stored per day as JSONL for the plugin's own queries and as CSV so DuckDB can analyze it with SQL; the workbench generates ready-to-run queries with the real file paths filled in. - Workbench: receiver status with the actually bound endpoints, trace list with service/error/duration filters, span waterfall, metrics and logs, and an SQL analysis tab. - Result view renders any span-shaped query result as a waterfall. - Connection provider exposes listen host/port, gRPC port, retention days, autostart and an optional ingest token. - Preferred ports 4318/4317 fall back to ephemeral ports and the UI reports the real endpoint, since these are machine-wide resources often held by a local collector. - Tests cover decode/persist/aggregate, port fallback, token enforcement, retention, root-span resolution independent of export order, and end-to-end ingest through the official OpenTelemetry Go SDK over both transports.