Introducing OTel Blueprints and Reference Implementations

It’s not uncommon for end users adopting OpenTelemetry to, at some point in their journey, ask themselves: “Why is this stuff so complex?” . Full adoption normally requires understanding the different ways of configuring SDKs, multiple Collector deployments, data pipelines, instrumentation libraries, semantic convention registries, APIs for manual instrumentation across many different programming languages, and many other moving pieces. These moving pieces don’t operate in isolation either.