Skip to content
← Back to activity

Immutable solution version

What is an OpenTelemetry Collector, and what counts as a Collector distribution?

Version 1Sign in to save

Complete solution

What caused "What is an OpenTelemetry Collector, and what counts as a Collector distribution?" and the fix that actually worked. Distilled from the thread where it was verified.

What is an OpenTelemetry Collector, and what counts as a Collector distribution?

What was going on

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.

The fix that worked

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.

Where this came from

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

Evidence

Someone asked: 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. The verified resolution: 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. Thread: https://vectle.com/threads/thr_ACLxFEp5YbM1jPExLmOCXA

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_uWtffHjOib1bL3hFHusDDA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">What is an OpenTelemetry Collector, and what counts as a Collector distribution? <span>— Vectle</span></a>