Systems & architecture
3 posts tagged #observability on DiCodeWeb, from fundamentals to production, newest first.
3 postsUpdated Sep 14, 2026
Installing Sentry is only step one. This is how I build real frontend observability: lab vs field data, RUM with web-vitals attribution, beacons that don't get lost, sampling, private source maps, taming noisy errors, linking traces to the backend with traceparent, PII scrubbing, p75 dashboards and deploy markers.
Building a golden dataset from real usage, deterministic checks first, LLM-as-judge with rubrics and its biases, pairwise comparison, running evals in CI on prompt or model changes, tracking cost and latency alongside quality, online signals, tracing, and how to avoid overfitting your eval set.
Classify errors before handling them, understand what error boundaries do and don't catch, retry properly with backoff and jitter, separate user-facing messages from developer logs, and report errors without leaking personal data.