open-telemetry
/
opentelemetry-collector-releases
mirror of https://github.com/open-telemetry/opentelemetry-collector-releases.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
opentelemetry-collector-rel.../distributions
History
Jonathan 8c2ee9dfb4
add prometheuswritereceiver to contrib collector (#1020) 
* add prometheuswritereceiver to contrib collector

* pr 1020

* remove prw to otelcolk8s and otelcol
 		2025-07-17 14:50:16 +00:00
..
otelcol Disable net/x/trace usage in gRPC (#1018) 2025-07-16 18:49:56 +00:00
otelcol-contrib add prometheuswritereceiver to contrib collector (#1020) 2025-07-17 14:50:16 +00:00
otelcol-ebpf-profiler Disable net/x/trace usage in gRPC (#1018) 2025-07-16 18:49:56 +00:00
otelcol-k8s Disable net/x/trace usage in gRPC (#1018) 2025-07-16 18:49:56 +00:00
otelcol-otlp Disable net/x/trace usage in gRPC (#1018) 2025-07-16 18:49:56 +00:00
README.md [chore] Require that all components in distributions are tagged and clarify what happens when rules change (#976) 2025-06-18 10:58:01 +00:00

README.md

Criteria for Supported Distributions

Support for a distribution implies all the duties covered by the Approver and Maintainer role requirements. In addition, support means that the Collector SIG is the owner and maintainer of the binaries/images of the different Collector distributions and is responsible for the pipeline that produces those artifacts.

The Collector SIG will support at least one distribution that is recommended for production which includes support for Prometheus, Jaeger, Zipkin, and OpenCensus.

Distributions supported by the Collector SIG should fulfill the following criteria:

  1. Serve a specific purpose that has minimal overlap with the purpose of any other distribution.
  2. Should meet general needs and be desired by many users.
  3. Should not be specific to any vendor.
  4. May be focused on development or proof of concept use cases. The distribution should clearly indicate whether the Collector SIG recommends the distribution be used in production environments.
  5. Must only include components from the open-telemetry org.
    • Components that are marked Unmaintained will be kept in any distributions for six months. After six months of being unmaintained the component will be removed from the distributions.
  6. Must only include components that are properly tagged as Go modules. Updates to components will only be considered if they correspond to a tag.
  7. Have a clearly defined list of criteria for which components are included.
  8. Must include the following assets except where the specific purpose of the distribution is naturally associated with a subset of these assets. In such cases, it should be clearly stated which assets are skipped and why. Additional assets may be included if the maintainers agree:
    • Binaries for linux_amd64, linux_arm64, windows_amd64 and darwin_arm64
    • linux_amd64 and linux_arm64 container images
    • Packages to be used with Linux distributions (RPM, deb), macOS (brew), Windows (MSI) for each distributed binary.

After any change to these rules, distribution owners will have 1 month to comply with any new requirements. Maintainers will make a best effort to ensure that distribution owners are notified of any changes to the rules that may affect their distribution. If a distribution does not comply with the new requirements, it MAY be marked as deprecated after one month and eventually be removed from the list of supported distributions.