[BLCCoreStudio]

Summary

Upgrades cloud/opentelemetry from a compact schema-v1 overview into a schema-v3 deep technical reference organized around OpenTelemetry's real interoperability layers: specification, API, SDK, instrumentation, Resources, Instrumentation Scope, context propagation, semantic conventions, signals, OTLP, and Collector pipelines.

Changes

• distinguish OpenTelemetry from storage/query/visualization backends and separate specification, API, SDK, instrumentation, and Collector responsibilities
• document Resources, service identity, Instrumentation Scope, semantic conventions, context propagation, Baggage, and trust boundaries
• cover traces/spans/events/links, head and tail sampling, metrics instruments/temporality/histograms/exemplars, logs/correlation, and evolving signals
• explain OTLP gRPC/HTTP transport, protocol maturity, hop-by-hop delivery semantics, batching, retry, and failure boundaries
• cover Collector receivers, processors, exporters, connectors, extensions, pipelines, Agent/Gateway topologies, queues, persistent storage, scaling, tail-sampling affinity, and internal telemetry
• add Prometheus interoperability, backend portability, dual export/migration, Kubernetes deployment patterns, security/privacy, cardinality, and performance guidance
• add failure modes, debugging workflows, semantic-convention migration, telemetry governance, reliability design, anti-patterns, operational checklist, and staged learning path
• add Technology Universe coverage metadata and a deliberate typed relationship to Prometheus
• verify Apache-2.0 and expand primary sources to current upstream specification, semantic-convention, OTLP, signal, SDK, and Collector documentation

Quality bar

This follows the project's deep-dive standard without treating OpenTelemetry as one monolithic product or implying uniform feature maturity across every SDK, Collector distribution, signal, or backend. The organizing model is interoperability plus the identity, transport, processing, durability, and cost boundaries operators need to reason about.