Diagnostics and analytics
DM records operational diagnostics by default. Turn them off in the web Account
page, with dm config telemetry false, with Client::with_telemetry(false), or
with DM_TELEMETRY_ENABLED=false on the backend. dm config telemetry true
reenables the CLI and daemon. CLI configuration and the environment override apply
to both HTTP requests and shared WebSocket subscriptions. Web settings reconnect
open sockets so the new preference takes effect.
Where events go
Production events use the dedicated tos / silicondm table in
Space Station.
Only the backend holds DM_SPACE_STATION_TABLE_KEY. It uses the official
space-station Rust package 0.1.1, whose local daemon spools records and ships them
with acknowledgements. The SDK, CLI and browser use DM's authenticated
POST /api/v1/telemetry endpoint; the ingest credential is never shipped in a
browser bundle or a CLI binary.
Sandbox diagnostics are written to that sandbox's telemetry_events table and
never exported through the production Space Station key. Generation fences reject
late writes after a clean. Cleaning a sandbox also clears its diagnostics.
What is captured
Events contain a schema version, DM version, source, event, environment and process identity. HTTP events add the route template, method, request ID, response status, success and duration. Connection events include session identity and close code. CLI completion, daemon queue checks and callback outcomes, and browser page views, request timings and error classifications provide client-side context. Space Station adds system and ingestion metadata itself.
The browser analytics path is explicit and goes through the same authenticated DM gateway as product requests. DM does not use a third-party browser script or expose the table key. Diagnostic input accepts a small fixed set of event types and numeric/boolean fields. Message bodies, drafts, attachment links, callback URLs, SLTs, access tokens, app secrets, webhook bodies and exception strings are excluded.
Operate the exporter
Set DM_SPACE_STATION_TABLE_KEY in the API service's secret environment and set
DM_TELEMETRY_HOME to a private writable durable directory. The default spool is
/tmp/silicon-dm-telemetry, which survives process restarts on the same filesystem
but not replacement of an ephemeral container. Mount persistent storage when
retaining unsent diagnostics across container replacement is required.
Production Fargate tasks use a private UID 10001, mode 0700 volume at
/var/lib/silicon-dm/telemetry. This volume lasts for the task; replacement
can discard unsent diagnostics.
Diagnostics are best effort and never gate message delivery. The official SDK bounds its pending queue; sandbox writes have a separate bounded concurrency limit. A missing ingest key leaves production export inactive, while explicit opt-out disables recording. Keep the Space Station daemon/spool accessible to the backend process and inspect the dedicated table for delivery verification.
Useful query:
SELECT record.source, record.event, count() AS n
FROM silicondm
GROUP BY record.source, record.event