Getting Started • Getting Involved • Getting In Touch
Contributing • Vision • Design • Monitoring • Performance • Roadmap
This is a repository for OpenTelemetry Collector contributions that are not part of the core repository and core distribution of the Collector. Typically, these contributions are vendor specific receivers/exporters and/or components that are only useful to a relatively small number of users.
Please note that this repository and its releases are a superset of the core repository.
A guide on how to create your own distribution is available in this blog post: "Building your own OpenTelemetry Collector distribution"
If you are building your own distribution, the OpenTelemetry Collector Builder might be a good starting point.
See CONTRIBUTING.md.
Triagers (@open-telemetry/collector-contrib-triagers)
- Andrew Hsu, Lightstep
- Steve Flanders, Splunk
Approvers (@open-telemetry/collector-contrib-approvers):
- Anuraag Agrawal, AWS
- Dmitrii Anoshin, Splunk
- James Bebbington, Google
- Jay Camp, Splunk
- Juraci Paixão Kröhling, Red Hat
- Kevin Brockhoff, Daugherty Business Solutions
- Nail Islamov, Google
- Owais Lone, Splunk
Maintainers (@open-telemetry/collector-contrib-maintainer):
- Bogdan Drutu, Splunk
- Tigran Najaryan, Splunk
Learn more about roles in the community repository.
When creating a PR please following the process described here.
News PRs will be automatically associated with the reviewers based on CODEOWNERS. PRs will be also automatically assigned to one of the maintainers or approvers for facilitation.
The facilitator is responsible for helping the PR author and reviewers to make progress or if progress cannot be made for closing the PR.
If the reviewers do not have approval rights the facilitator is also responsible for the official approval that is required for the PR to be merged and if the facilitator is a maintainer they are responsible for merging the PR as well.
The facilitator is not required to perform a thorough review, but they are encouraged to enforce Collector best practices and consistency across the codebase and component behavior. The facilitators will typically rely on codeowner's detailed review of the code when making the final approval decision.
We recommend maintainers and approvers to keep an eye on the project board. All newly created PRs are automatically added to this board. (If you don't see the PR on the board you may need to add it manually by setting the Project field in the PR view).