We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We will need to define plan and requirements for making components SemConv compliant before their graduation.
For example hostmetrics receiver will go through this process at some point: open-telemetry/opentelemetry-collector-contrib#35325
hostmetrics
I foresee K8s components will follow this path.
Originally posted by @ChrsMark in #11864 (comment)
The text was updated successfully, but these errors were encountered:
I think we can add this to a more general "specification compliance" requirement (since semantic conventions are part of the specification)
Sorry, something went wrong.
No branches or pull requests
We will need to define plan and requirements for making components SemConv compliant before their graduation.
For example
hostmetrics
receiver will go through this process at some point: open-telemetry/opentelemetry-collector-contrib#35325I foresee K8s components will follow this path.
Originally posted by @ChrsMark in #11864 (comment)
The text was updated successfully, but these errors were encountered: