You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Desired feature or idea: Components in the OpenTelemetry Collector repositories have a metadata.yaml file (example) that documents the stability of the component across several signals.
Stability definitions are available here and follow OTEP 232 definitions. Making this information available on the opentelemetry.io website would help users understand what components are mature enough to be used in their build depending on their requirements.
Additional context: We would like to have this information available in the registry for the Collector 1.0 distro.
The text was updated successfully, but these errors were encountered:
I created open-telemetry/community#2246 to address this project-wide, but independent of that, we should try to address this need from the collector SIG.
The easiest is probably taking the status from the metadata YML and copy it into the registry YML and then turn that into a workflow that checks for changes and transfers that to the otel.io repo.
Desired feature or idea: Components in the OpenTelemetry Collector repositories have a
metadata.yaml
file (example) that documents the stability of the component across several signals.Stability definitions are available here and follow OTEP 232 definitions. Making this information available on the opentelemetry.io website would help users understand what components are mature enough to be used in their build depending on their requirements.
Additional context: We would like to have this information available in the registry for the Collector 1.0 distro.
The text was updated successfully, but these errors were encountered: