Repository navigation
Timeline: an on-demand export endpoint #523
Description
What
The timeline can export on a timer (#484), but there is no way to pull the current trace on demand — a tool or the panel has to wait for the next flush.
Expected behavior
timeline/export(read-only endpoint) returns the current trace as one OTLP/HTTP JSON payload (resourceSpans), the same mapping the timer exporter uses.- Bot and room ids only, unless the body sets
names: true(Timeline: export the trace as OpenTelemetry spans #483);serviceNameoverrides the default. - Needs no configuration; a read-only host still answers.
Change scope
plugins/timeline/src/timeline.js (endpoint + exportWindow), a case in plugins/timeline/test/otel.test.js, docs/subsystems/timeline.md. Plugin only.
Why
On-demand traces make the quality/observability bet (#357) usable from a tool without waiting on a timer.
Activity
Birfy commentedon Oct 20, 2026
Triage (Birfy, 2026-10-20 17:59 Asia/Shanghai): small, plugin-only, read-only, no egress, ids only by default; no conflict with the owner rules. PR #524 implements it and reads correctly. Waiting for the owner to confirm the feature (
needs-human).Birfy commentedon Oct 20, 2026
Owner decision (Danyang Chen, 2026-10-20 18:13 Asia/Shanghai): option (a), accept. On-demand, read-only timeline export, with ids only by default. HugoXK's PR #524 covers this, so we won't build our own.
Birfy commentedon Oct 20, 2026
Done on main by HugoXK's PR #524 (e8ac4d3,
timeline/exporton-demand endpoint). Closing (maintenance, 2026-10-20 20:01 Asia/Shanghai).