---

Getting Started   •   Getting Involved   •   Getting In Touch

Vision   •   Design   •   Configuration   •   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.) 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.

Stability levels

The collector components and implementation are in different stages of stability, and usually split between functionality and configuration. The status for each component is available in the README file for the component. While we intend to provide high-quality components as part of this repository, we acknowledge that not all of them are ready for prime time. As such, each component should list its current stability level for each telemetry signal, according to the following definitions:

In development

Not all pieces of the component are in place yet and it might not be available as part of any distributions yet. Bugs and performance issues should be reported, but it is likely that the component owners might not give them much attention. Your feedback is still desired, especially when it comes to the user-experience (configuration options, component observability, technical implementation details, ...). Configuration options might break often depending on how things evolve. The component should not be used in production.

Alpha

The component is ready to be used for limited non-critical workloads and the authors of this component would welcome your feedback. Bugs and performance problems should be reported, but component owners might not work on them right away. The configuration options might change often without backwards compatibility guarantees.

Beta

Same as Alpha, but the configuration options are deemed stable. While there might be breaking changes between releases, component owners should try to minimize them. A component at this stage is expected to have had exposure to non-critical production workloads already during its Alpha phase, making it suitable for broader usage.

Stable

The component is ready for general availability. Bugs and performance problems should be reported and there's an expectation that the component owners will work on them. Breaking changes, including configuration options and the component's output are not expected to happen without prior notice, unless under special circumstances.

Deprecated

The component is planned to be removed in a future version and no further support will be provided. Note that new issues will likely not be worked on. When a component enters "deprecated" mode, it is expected to exist for at least two minor releases. See the component's readme file for more details on when a component will cease to exist.

Compatibility

When used as a library, the OpenTelemetry Collector attempts to track the currently supported versions of Go, as defined by the Go team. Removing support for an unsupported Go version is not considered a breaking change.

Starting with the release of Go 1.18, support for Go versions on the OpenTelemetry Collector will be updated as follows:

1. The first release after the release of a new Go minor version N will add build and tests steps for the new Go minor version.
2. The first release after the release of a new Go minor version N will remove support for Go version N-2.

Official OpenTelemetry Collector distro binaries may be built with any supported Go version.

Contributing

See the Contributing Guide for details.

Here is a list of community roles with current and previous members:

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

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

• Emeritus Triagers:

  • Andrew Hsu, Lightstep

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

  • Anthony Mirabella, AWS
  • Dmitrii Anoshin, Splunk
  • Juraci Paixão Kröhling, Grafana Labs
  • Pablo Baeyens, DataDog

• Emeritus Approvers:

  • James Bebbington, Google
  • Jay Camp, Splunk
  • Nail Islamov, Google
  • Owais Lone, Splunk
  • Rahul Patel, Google
  • Steven Karis, Splunk
  • Yang Song, Google

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

  • Alex Boten, Lightstep
  • Bogdan Drutu, Splunk
  • Tigran Najaryan, Splunk

• Emeritus Maintainers:

  • Paulo Janotti, Splunk

Learn more about roles in Community membership. In addition to what is described at the organization-level, the SIG Collector requires all core approvers to take part in rotating the role of the release manager.

Thanks to all the people who already contributed!