API Observability by Design: Building Systems That Tell Their Own Stories
summary
Argues for treating observability as visualization-first, product-driven metrics and shows concrete wiring: hook an OpenTelemetry + Jaeger + Prometheus + Grafana stack via the OTEL Java agent, expose Micrometer metrics from Micronaut, and push business metrics (data stored, retrieval counts) alongside logs and traces. Claims 1.88M emails/day and petabytes of storage drove the need for low-cardinality dashboards, standardized OTEL agents, and alerts as a fourth pillar; demos run locally (producer + store) to prove it’s practical.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 7:44Observability as storytelling
- 13:09Legacy systems' observability gaps
- 20:13Visualization first
- 28:07Three pillars of observability
- 39:25Standardizing observability
- 43:40Key takeaways and closing thoughts
related talks
01h 10mObservability For (Java) Devs - 2023 Edition
31mCharting New Frontiers: The Evolution of Observability in Cloud Environments
13mArchitecting an open observability stack
33mWhat Developers Should Know About Observability
35mBeyond Logs, Metrics and Traces. The Data Analytics Paradigm Shift in Observability — Dotan Horovits
01mObservability
38mObservability 101 with Spring and Micrometer
43mObservability Visualization in the Age of OpenTelemetry