
Software Engineering Radio - the podcast for professional software developers SE Radio 717: Eric Tschetter on Decoupling Observability
Apr 23, 2026
Eric Tschetter, co-founder of Apache Druid and Chief Architect at Imply, shares perspectives from building large analytics and observability systems. He explains why decoupling logs, metrics, and traces helps avoid vendor lock-in and scale pain. He outlines a four-layer architecture, the role of OpenTelemetry, query/compute trade-offs, indexing strategies, and practical migration, governance, and operational concerns.
AI Snips
Chapters
Transcript
Episode notes
Observability Is Following BI's Decoupling Trajectory
- Observability/security follow the BI evolution but lag because BI had decades to separate visualization, data storage, and ETL.
- BI decoupled after SQL became a de facto interface; observability lacks a single query standard, slowing decoupling.
Query Languages, Not Schemas, Are The Key To Portability
- The core barrier to observability decoupling is multiple query languages (SPL, LogQL, KQL, promQL) rather than the raw data shape.
- Unifying by supporting many query APIs on one data layer is the practical path to portability.
Standardize On Query APIs Not Universal Schemas
- Standardize interfaces, not schemas: implement query APIs so teams can use familiar tools against shared data.
- Treat standards as de facto: adopt popular query interfaces and expose them on your central data layer for interoperability.

