OpenTelemetry

Fact sheet

OpenTelemetry is an open-source observability framework under the CNCF. It supplies common APIs, SDKs, semantic conventions, and protocols for telemetry; it is explicitly not an observability backend [1].

Field	Finding
Entity type	Standard and enabling technology; open-source project
Governance	Cloud Native Computing Foundation project
License	Apache 2.0 for the main project repositories
Signals	Traces, metrics, logs, and profiles; component maturity varies
Deployment	Libraries, agents, gateways, and collectors
Storage	None provided as a general backend
Commercial model	Open source; commercial distributions and services exist

Collection and export

The Collector receives, processes, and exports telemetry through configured pipelines [2]. Its component model can reduce tight coupling to one backend. Portability still depends on semantic conventions, supported components, proprietary extensions, and whether queries, alerts, and historical data can move.

Best fit

OpenTelemetry fits teams that need consistent instrumentation, multiple destinations, or an open collection layer. It is unsuitable as a standalone answer to storage, search, visualization, alerting, access control, or incident workflows.

Shared technology-map evidence

The map assigns three of twelve families: telemetry generation and instrumentation, collection and processing, and export through vendor-neutral pipelines [1], [2]. The cost reference is a small implementation and operations allowance rather than a software fee. Its broad bubble reflects support by more than 90 observability vendors in the official documentation and 7,400-plus stars in the Collector repository when reviewed [3].

Evidence state

Core classification is directly supported by project documentation. Interoperability should be tested against chosen languages, collectors, processors, and destinations. Performance and operational overhead remain environment-specific.