OpenTelemetry cited as observability standard

OpenTelemetry’s graduation by the Cloud Native Computing Foundation this month has given new momentum to a claim already common across infrastructure teams: that the project has become the common language for observability data. CNCF lists OpenTelemetry as moving to graduated status on May 11, 2026, and the OpenTelemetry project published its own announcement on May 21. The milestone matters because OpenTelemetry is no longer just a tracing library or a developer tool. The project describes itself as a vendor-neutral framework for generating, collecting and exporting traces, metrics and logs, and its documentation says it is supported by more than 90 observability vendors. ### Why are people calling OpenTelemetry a standard now? CNCF graduation is a governance and maturity signal, not a legal standard. (cncf.io) But CNCF’s project page shows OpenTelemetry progressing from accepted status in 2019 to incubating in 2021 and graduated in 2026, while the OpenTelemetry project says the framework is already “used across the industry.” OpenTelemetry’s own documentation also uses standard-setting language. (opentelemetry.io) The docs call it an “industry-standard” framework for traces, metrics and logs, and emphasize that instrumentation can be exported to multiple back ends rather than tied to one vendor. ### What changed with Databricks Zerobus? Databricks said on April 9 that Zerobus Ingest added native support for the OpenTelemetry Protocol, or OTLP, through a built-in endpoint in its ingestion service. (cncf.io) Databricks said that lets customers stream traces, logs and metrics directly into Unity Catalog Delta tables using standard OpenTelemetry SDKs and collectors, without custom libraries. (opentelemetry.io) The company’s documentation says Zerobus Ingest OTLP is in beta and currently supports OTLP over gRPC, with separate services for traces, logs and metrics. Databricks also says the service supports partial success responses, gzip compression and a default quota of 10,000 requests per second. ### What does “code-free ingest” actually mean here? Databricks does not describe the feature as fully “code-free” in its formal documentation. (community.databricks.com) What it does say is that standard OpenTelemetry SDKs and collectors can send data to Zerobus Ingest “without custom libraries,” and that existing OTLP-compatible exporters can point at the endpoint. That means teams can use existing collectors and exporters rather than writing a custom ingestion layer. (docs.databricks.com) Databricks’ April 9 product post said no custom libraries or intermediary pipelines are required, and its docs say users still need to create target tables in advance and configure headers and credentials. (docs.databricks.com) ### What about PII masking and private connectivity? Databricks’ official OTLP and Zerobus documentation reviewed here confirms private connectivity for Zerobus through inbound PrivateLink for performance-intensive services on AWS. That page says the feature allows private connections to services such as Zerobus Ingest and is in public preview. (community.databricks.com) The same official sources did not substantiate a built-in PII masking feature specific to Zerobus OpenTelemetry ingest. Databricks’ OTLP docs focus on transport, schemas, quotas, target tables and Unity Catalog integration, and the product and community posts reviewed do not describe native PII masking as a documented Zerobus OTLP capability. ### So what is the practical takeaway for enterprise teams? (docs.databricks.com) OpenTelemetry’s May 2026 graduation gives enterprises a stronger signal that the project is mature enough to anchor logging, tracing and metrics pipelines across vendors. Databricks’ April 9 release shows how vendors are now building products around OTLP as a default ingestion format rather than treating it as an add-on. (docs.databricks.com) Databricks’ next concrete step is still product rollout rather than a new announcement. The OTLP endpoint is listed as beta in documentation last updated April 9, 2026, while Zerobus Ingest itself is already generally available, according to a Databricks community post published on February 23. (docs.databricks.com) (opentelemetry.io)