Status, 2026-09-09: release candidate, load-tested. The SDK (ashlar-trace), server
(ashlar-trace-server), dashboard, demo hosts and guides are built; the SDK is tested end to end
against the real server; a bug review of the SDK and a security review of the server are done and
their findings fixed. Moved into ashlar with its history; apps use it through ashlar-telemetry.
Not yet published.
Find why ingest latency collapses at 2,000 envelopes a second once the database passes about 3 GB. Suspected: index inserts outgrowing the cache; not proven.
Cut ingest tail latency while retention deletes a large backlog (p99 about 300 ms against about 50 ms).
Repeat the load runs on Linux and on a quiet machine; all numbers so far are from one busy macOS machine.
Build and run the container image once (deploy/trace/Dockerfile, deploy/trace/compose.yml). Written but never built.
Run the windowed demo (examples/trace-demo-gui). It compiles and passes lints but has never been opened.
Check the dashboard on a narrow (360 px) screen.
Check the login cookie (Secure, __Host- prefix) in a browser over real HTTPS.
Decide whether to prove “no allocation” for the realtime counters, which needs an unsafe exemption for one test file.