Six pillars of telemetry TEMPLE Yuri Shkuro META

Yuri Shkuro Software Engineer Meta shkuro.com CNCF Jaeger
 Founder & Maintainer jaegertracing.io CNCF OpenTelemetry Co-founder, GC & TC opentelemetry.io Mastering Distributed Tracing Author


OpenTelemetry yesterday Logs Metrics Traces “Three pillars”

MELT Logs Metrics Traces Events

Logs Metrics Traces Events OpenTelemetry tomorrow
 (TEMPL) Profiles

Blog post: https://bit.do/telemetry-temple TEMPLE - Six Pillars of Telemetry E - Exceptions L - Logs P - Profiles M - Metrics E - Events T - Traces Photo by Dario Crisafulli on Unsplash

Metrics The original pillar Bad for troubleshooting Great for monitoring Operational data Dimensional Aggregatable Numerical

Logs The ancient pillar Hard to correlate Expensive Localized (easy sharding) Schematized Semi-structured Unstructured

Traces The “new cool kid on the block” pillar Root cause isolation, and more End-to-end monitoring Distributed (hard to bill for usage) Capture causality (DAG) Workflow centric Request-scoped logs

Events The misunderstood pillar Lower volume Strong identity High reliability requirement Shape: structured logs Change events Everything is an “event”

Profiles The geek pillar Aggregatable Large data volumes No instrumentation required Power user tool Lower usage Know when you see it

Exceptions The forgotten pillar Custom UI Special processing pipeline Aggregatable * Peek inside the frames Super-structured logs

Conclusion Don’t take it seriously There are more than “3 pillars” The term TEMPLE is awesome The boundaries are diffuse Pillars ≠ observability, just data

Come to my talk Thursday, 27 Oct, 16:00–16:25 Yuri Shkuro, Benjamin Renard, and Atul Singh. 2022. Positional Paper: Schema-First Application Telemetry. SIGOPS Oper. Syst. Rev. 56, 1 (June 2022), 8–17. https://doi.org/10.1145/3544497.3544500

Q&A Thank You Find me @ https://shkuro.com