Session Telemetry

Session Telemetry

Upstream optional capability — not implemented in Edge.

Upstream reference: Session Telemetry documentation

What Upstream Provides

Session telemetry is an optional capability seam that exports session event data for external analysis. It has two components:

• dsh-session-telemetry — coordinator: captures session events, applies redaction waterfall, emits structured records with dual channels (ledger for event mirrors, ops for operational signals).
• dsh-session-telemetry-otel — provider: implements the SessionTelemetrySink interface using OpenTelemetry JS SDK log pipeline.

The upstream documentation states: "telemetry is an optional capability, not part of the agent loop backbone, and nothing here enters model requests."

Edge Status

Not Implemented Neither the coordinator nor the provider is installed. @deepseek-ai/dsh-anonymous-user-id is listed in dependencies but no plugin is activated. No session events are exported, no usage tracking occurs, and no OpenTelemetry pipeline exists.

This is intentional: Edge is a self-hosted, single-user deployment. Telemetry export requires a receiving backend (OpenTelemetry collector) and a sharing policy — neither of which is configured in the Edge deployment model.

TODO

Evaluate telemetry for self-hosted usage analytics. (#94) If users want to track their own usage (token consumption, session counts, tool call frequency), the upstream telemetry seam could be adapted with a DO-local sink instead of OpenTelemetry export. This would keep data within the Durable Object rather than requiring external infrastructure.