OpenTelemetry adoption requires treating it as an operating model, not just a tool swap. The real value lies in preserving context through semantic conventions and resource attributes, enabling automatic correlation across logs, metrics, and traces. A "Collector First" architecture is recommended, with lightweight edge collectors near applications and centralized gateway collectors for heavy processing. The strangler pattern enables gradual migration, starting with Kubernetes environments. Combining auto-instrumentation (70-80% coverage) with manual instrumentation for business-specific attributes provides the most mature approach. Success requires clear ownership of schemas, validation tools like Weaver, and maintaining OTLP at the edge for true vendor agnosticism.
