~/observability
This site is observed.
Real SLOs with a visible error budget, real-user Web Vitals, and synthetic probes — for a personal website, because measuring reliability is the job. All of it without cookies, identifiers, or tracking of any kind.
- —
- availability, since launch target ≥ 99.9% · synthetic, 5-min checks …
- —
- error budget remaining of allowed downtime in the window
- —
- LCP p75, real users, 7 days target < 1.5s …
- —
- requests, 24h (CloudFront edge) error rate: —
status.json isn’t published yet — the pipeline is collecting its first data. Check back soon; the publisher runs hourly.
Note: availability is measured from 6 August 2026, when this site went into service, on a rolling 30-day window thereafter. Before that date the domain was deliberately unpointed while I was still verifying the claims on these pages — probe failures from that period record a configuration I chose, not unplanned downtime, which is the thing an error budget exists to measure. Nothing inside the window is excluded or reset: an error budget you rewrite when it looks bad isn’t an error budget.
view as table
| day | availability % |
|---|
view as table
| hour | p75 ms |
|---|
web vitals — real users, 7 days
- —
- CLS p75
- —
- INP p75
- —
- TTFB p75
- —
- RUM samples
the pipeline
How the sausage is measured.
why it looks like this
Right-sized on purpose.
At 10,000-device scale, this job belongs to a custom OpenTelemetry Collector feeding SLO-backed alerting — I’ve built that. For one static page, an OTel pipeline would be theater: the right-sized version is a 2KB purpose-built beacon, two tiny Lambdas, and CloudWatch's embedded metric format. Same discipline — SLIs first, SLOs as code, error budgets you can see — sized for the system it observes.
The beacon observes pages, not people: no cookies, no identifiers, no fingerprinting, and it honors Do Not Track. Separately, the CDN keeps standard access logs — including client IP — for 90 days, first-party only, never shared or sold. Two different jobs: the beacon measures the experience, the logs record the traffic. The whole pipeline is in the public repo.