open-telemetry/opentelemetry-collector-contrib — explained in plain English
Analysis updated 2026-06-26
Add a Datadog or Honeycomb exporter to your OpenTelemetry Collector setup to ship traces to your preferred observability platform.
Use a contrib processor to filter or transform telemetry data before it leaves your infrastructure.
Build a custom lean Collector binary containing only the specific components your stack needs, reducing attack surface and binary size.
Ingest logs or metrics from a specific system using a contrib receiver not available in the core Collector.
| open-telemetry/opentelemetry-collector-contrib | cdk-team/cdk | crazy-max/diun | |
|---|---|---|---|
| Stars | 4,654 | 4,654 | 4,653 |
| Language | Go | Go | Go |
| Setup difficulty | moderate | easy | moderate |
| Complexity | 4/5 | 4/5 | 2/5 |
| Audience | ops devops | ops devops | ops devops |
Figures from each repo's GitHub metadata at analysis time.
Requires Go build environment, best used with the OTel Collector Builder to avoid shipping the full contrib binary.
OpenTelemetry is an open-source project that helps software teams collect data about how their applications are behaving in production: things like request traces, performance metrics, and log events. The Collector is the piece that sits between your running software and whatever system you use to store and analyze that data. It receives telemetry, processes it, and ships it onward. This repository, "opentelemetry-collector-contrib", is the community extension warehouse for the Collector. The core Collector repository contains the stable, officially maintained components. This contrib repository is where components live that are either experimental, vendor-specific, or maintained by individual contributors rather than the core team. Examples of things you find here include connectors to specific observability platforms, processors for transforming or filtering data, and receivers that can ingest telemetry from particular systems. Each component in this repository carries a stability label, which can be Development, Alpha, Beta, or Stable. A single component can be at different stability levels for different signal types: for example, it might be Stable for traces but still Alpha for metrics. The README is clear that the contrib maintainers may downgrade or remove components if they are no longer actively maintained. Support for any given component comes either from the broader community of contrib maintainers, or from a specific vendor that contributed and owns that component. The maintainers listed in the README represent engineers from companies including Honeycomb, Elastic, Splunk, Snowflake, Dynatrace, DataDog, and others. Users who want a lean setup are encouraged to build a custom Collector distribution containing only the components they actually need, rather than shipping the full contrib binary. A tool called the OpenTelemetry Collector Builder is provided for that purpose. The repo is part of the larger OpenTelemetry project under the Cloud Native Computing Foundation.
This is the community extension library for the OpenTelemetry Collector, a middleware tool that collects performance traces, metrics, and logs from your app and routes them to Datadog, Splunk, Honeycomb, or any other analytics platform.
Mainly Go. The stack also includes Go, OpenTelemetry, CNCF.
Apache 2.0, use freely for any purpose including commercial, keep copyright notices intact.
Setup difficulty is rated moderate, with roughly 1h+ to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.