Unlocking Business Insights with OpenTelemetry
summary
A prototype implements OpenTelemetry emitters and tiered global collector plus local collectors to drive feedback loops that auto‑provision clusters, anonymize tenant data, and tie billing to business units (job nodes) rather than raw API calls. It runs sample services in Go with .NET client examples, handles extremely dynamic fleets—think 100,000 short‑lived containers—and demonstrates autoscaling across clusters, accurate consumption billing, and dashboards for tenants. The prototype works and the Chef 360 product moves toward GA with these mechanisms.
AI-written summary · about
chapters (15)
- 0:00Introduction to Telemetry and OpenTelemetry
- 0:24Challenges with Traditional Telemetry
- 1:21Agenda Overview
- 1:56Importance of Telemetry Data
- 2:09Chef 360: Multi-Tenant SaaS Application
- 2:39Customer Behavior and MELT Model Challenges
- 4:34Telemetry-Driven Approach for Scalability
- 4:57Enterprise Application Lifecycle
- 5:40Telemetry for Multi-Tenant Systems
- 7:10Capturing and Using Telemetry Data
- 8:49OpenTelemetry Implementation
- 14:20Prototype and Technical Details
- 18:31Animation Demonstration
- 20:51New vs. Old Solutions
- 26:25Conclusion and Resources
related talks
35mOpenTelemetry for Busy People
22mOpenTelemetry – An Observability Framework for Cloud-Native Software
50mOpen Source Instrumentation - The Rise of OpenTelemetry
37mObservability For You And Me With Opentelemetry
38mThe State of OpenTelemetry
31mUnlocking the Power of OpenTelemetry: Enhancing Design, Development...
55mCloud-Native Observability with OpenTelemetry
30mOpenTelemetry 101