<p align="center"> <strong> <a href="https://opentelemetry.io/docs/collector/getting-started/">Getting Started</a>   •   <a href="CONTRIBUTING.md">Getting Involved</a>   •   <a href="https://gitter.im/open-telemetry/opentelemetry-service">Getting In Touch</a> </strong> </p> <p align="center"> <a href="https://goreportcard.com/report/github.com/open-telemetry/opentelemetry-collector"> <img alt="Go Report Card" src="https://goreportcard.com/badge/github.com/open-telemetry/opentelemetry-collector?style=for-the-badge"></a> <a href="https://circleci.com/gh/open-telemetry/opentelemetry-collector"> <img alt="Build Status" src="https://img.shields.io/circleci/build/github/open-telemetry/opentelemetry-collector?style=for-the-badge"></a> <a href="https://codecov.io/gh/open-telemetry/opentelemetry-collector/branch/main/"> <img alt="Codecov Status" src="https://img.shields.io/codecov/c/github/open-telemetry/opentelemetry-collector?style=for-the-badge"></a> <a href="https://github.com/open-telemetry/opentelemetry-collector/releases"> <img alt="GitHub release (latest by date including pre-releases)" src="https://img.shields.io/github/v/release/open-telemetry/opentelemetry-collector?include_prereleases&style=for-the-badge"></a> </p> <p align="center"> <strong> <a href="docs/vision.md">Vision</a>   •   <a href="docs/design.md">Design</a>   •   <a href="docs/monitoring.md">Monitoring</a>   •   <a href="docs/performance.md">Performance</a>   •   <a href="docs/security.md">Security</a>   •   <a href="docs/roadmap.md">Roadmap</a>   •   <a href="https://pkg.go.dev/go.opentelemetry.io/collector">Package</a> </strong> </p>

Getting Started   •   Getting Involved   •   Getting In Touch

Vision   •   Design   •   Monitoring   •   Performance   •   Security   •   Roadmap   •   Package

OpenTelemetry Collector

The OpenTelemetry Collector offers a vendor-agnostic implementation on how to receive, process and export telemetry data. In addition, it removes the need to run, operate and maintain multiple agents/collectors in order to support open-source telemetry data formats (e.g. Jaeger, Prometheus, etc.) sending to multiple open-source or commercial back-ends.

Objectives:

• Usable: Reasonable default configuration, supports popular protocols, runs and collects out of the box.
• Performant: Highly stable and performant under varying loads and configurations.
• Observable: An exemplar of an observable service.
• Extensible: Customizable without touching the core code.
• Unified: Single codebase, deployable as an agent or collector with support for traces, metrics and logs.

Status

The collector components and implementation are in different stages of stability, and usually split between functionality and configuration:

Signal	Component	Status
Trace	OTLP protocol	Stable
	OTLP receiver functionality	Stable
	OTLP receiver configuration	Beta
	OTLP exporter functionality	Stable
	OTLP exporter configuration	Beta
Metric	OTLP protocol	Stable
	OTLP receiver functionality	Stable
	OTLP receiver configuration	Beta
	OTLP exporter functionality	Stable
	OTLP exporter configuration	Beta
Logs	OTLP protocol	Beta
	OTLP receiver functionality	Beta
	OTLP receiver configuration	Beta
	OTLP exporter functionality	Beta
	OTLP exporter configuration	Beta
Common	Logging exporter	unstable
	Batch processor functionality	Beta
	Batch processor configuration	Beta
	MemoryLimiter processor functionality	Beta
	MemoryLimiter processor configuration	Beta

We follow the production maturity level defined here

Contributing

See CONTRIBUTING.md.

Triagers (@open-telemetry/collector-triagers):

• Alolita Sharma, AWS
• Punya Biswal, Google
• Steve Flanders, Splunk

Approvers (@open-telemetry/collector-approvers):

• Alex Boten, Lightstep
• Anthony Mirabella, AWS
• Dmitrii Anoshin, Splunk
• Juraci Paixão Kröhling, Grafana Labs
• Owais Lone, Splunk

Maintainers (@open-telemetry/collector-maintainers):

• Bogdan Drutu, Splunk
• Tigran Najaryan, Splunk

Learn more about roles in the community repository.

Thanks to all the people who already contributed!