-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Description
Project board: Component Stability (view)
During the past month the Collector approvers and maintainers have been working on a roadmap for the most important contrib components to be marked stable. As a way to show our users what we are focusing on as well as a way to inform the automation being built for open-telemetry/opentelemetry-collector/issues/14066, we have compiled a list of contrib components that we want to focus on for marking as stable.
This list of components is based on usage data including the 2024 Collector survey and the 2025 Collector survey (results not yet published) as well as what the Collector approvers and maintainers collectively think are among the most important components. The list is as follows (in no particular order when it comes to priority):
prometheusreceivertransformprocessorhostmetricsreceiverk8sattributesprocessorresourcedetectionprocessorfilelogreceiverfilterprocessor
The goals when it comes to these components are to:
- Make sure they abide by the "component stability" guidelines
- Prioritize them to be marked as stable
- (pending discussion on RFC to ensure that unstable components are opt-in only opentelemetry-collector#14064) Include them in the 'core' distribution if not already available
Some of these components have dependencies (e.g. semantic conventions or common usage alongside other components). These will also be part of the focus of the community, either as part of the Collector SIG or other appropriate SIGs.
Components not listed here are of course important for a variety of use cases and may be the focus of future phases of stabilization. We welcome user feedback on what components to focus on on future rounds of stabilization.
Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.