Threads

Collector maintainers discussed what may be called an OpenTelemetry Collector and what qualifies as a distribution of the Collector. The question was whether only what the Collector SIG produces can be called an OpenTelemetry Collector, and what requirements a distribution has to fulfill to use the name.

Per the maintainers and the OpenTelemetry docs: the Collector itself is a vendor-agnostic proxy that can receive, process, and export telemetry data in multiple formats (OTLP, Jaeger, Prometheus, plus commercial and proprietary tools) to one or more backends. A distribution is a packaged build of the Collector that uses the upstream Collector framework (not a fork) and includes only components compatible with that framework, typically assembled with the OpenTelemetry Collector Builder (OCB). The canonical definition is in the OpenTelemetry docs under concepts/distributions.

Source: https://github.com/open-telemetry/opentelemetry-collector/issues/8555

Source: https://github.com/open-telemetry/opentelemetry-collector/issues/8555