Claim
A Go service receives one record per request from nginx over a Unix datagram socket, aggregates them per minute into exact SLI counts and mergeable exponential histograms in SQLite, and counts records lost in transit against nginx's own request counter. A lab burst of 200,000 requests showed the loss accounting exact (1,603 missing records counted, 1,603 send failures logged by nginx) and, after tuning the socket queue, no loss in three runs.
Status
- implemented
- Capped at Implemented: the code, tests and records are private, so this is self-reported and cannot be verified publicly.
- lab
- Local machine, local clusters or CI runners.
- personal lab
- My own projects. Public repositories carry CI-verified evidence; private ones are self-reported.
Source
A personal project whose repository is private and cannot be published. So this claim is self-reported: it stops at Implemented and links to no artifacts.
Limitations
- LIMITNot yet deployed; the lab figures come from one machine under synthetic load, not from this site's traffic.
- LIMITThe origin view sees only requests that reach the server; outages before nginx are invisible to it.
- LIMITThe repository is private, so the code and its tests cannot be inspected here yet.
- Source: private repository. The method and decisions are in ADR-0016 and ADR-0017.
Related claims
Implemented·environment:LabSelf-reported · private source
Each UTC day is published as hourly counters and histograms plus every statistic derived from them (SLIs with Wilson intervals, bucket-bounded percentiles, coverage, completeness, probe results), signed with Sigstore by a scheduled workflow; `ledger recompute` rebuilds every derived value from the observations and fails on any difference, including tampered counts, intervals, percentiles, probe results and replaced files.
SRE·Personal lab · no public artifactsEvidence →
Implemented·environment:LabSelf-reported · private source
CI builds and tests on GitHub-hosted runners and, for main only, signs a manifest of the tested image digests with Sigstore; the deploy refuses, before changing anything, any release whose signature, signing workflow, repository, branch, runner, trigger, commit or image digests do not match, using a verifier pinned outside the release.
Security·Personal lab · no public artifactsEvidence →