One YAML To Rule Them All: Declarative Config
summary
OpenTelemetry declarative configuration reaches a stable release after five years and lets one YAML file configure tracing and metrics across JavaScript, Java and C++ services, sending OTLP to a collector. The demo builds a polyglot app (Node, Java, C++) and shows saved traces that match programmatic setup, proving parity; editor help appears via schema store descriptions and VS Code autocompletion. Instrumentation-specific knobs remain work in progress. One YAML works in production now.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 2:49Limitations of environment variables
- 3:50Why declarative config
- 5:14Stable release & schema
- 7:02Demo setup & multi-lang
- 14:50Future of declarative config
- 17:37Recap & call to action
- 18:39Q&A
related talks
09mThe thin line between code and configuration (YAML/Helm rant)
20mKeynote: (Open)Telemetry Makes Observability Simple
30mFrom YANG To YAML: How We Tamed the 5G Configuration Beast
33mThe Observant Developer - OpenTelemetry from code to prod
06mLightning Talk: Not Just Enterprise. Modern Java App CI/CD Observability with OTel...
06mProject Lightning Talk: OTel 2025: The Latest Milestones and What’s Next
30mOpenTelemetry: The Road Ahead + Meet the Co...
20mStandardizing CI/CD Observability: Insights From the OpenTelemetry CI/CD SIG