Getting Started • Getting Involved • Getting In Touch
Vision • Design • Monitoring • Performance • Security • Roadmap • Package
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.
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
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
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!