Review components to give users an indication of the level of support

[codeboten]

As we do in the core component, we should label the components in the contrib repository to give users an insight as to what components are planned on being supported for the long term, versus which are experimental.

This requires a definition of what experimental, alpha, beta, stable for components in contrib. This would also need a dimension to specify components supported by a vendor.

Sub-tasks:

• Definition of the stability levels to be followed by each component #9379
• Define the stability and support level for the Loki Exporter #9380
• Define the stability and support level for the Routing exporter #9381
• Define the stability and support level for the Load balancing exporter #9382
• Add a command that lists components and their stability and support-levels #9518
• Add zpages information with the components' stability and support levels #9519

[codeboten]

The information to be captured:

Owners (who is supporting the component, vendor):
Status:

[codeboten]

The definition for stability should include:

• the interface with the user, the yaml configuration. The notion of stability for config and deprecation strategy should be defined as part of this.
• data produced by a component

[mx-psi]

To be done/discuss: add template for components to fill out (#9412 (comment))

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

[github-actions]

This issue has been closed as inactive because it has been stale for 120 days with no activity.