-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
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
Go semver seems not be consistant with otel semver spec #4922
Comments
Discover with : open-telemetry/opentelemetry-collector-contrib#31255 |
Can you please provide specifics of your issue? What semantic conventions are you missing? We generated v1.21.0 using the v1.21.0 version of semantic conventions. There shouldn't be anything missing. |
By semantic conv i refer to : https://opentelemetry.io/docs/specs/semconv/http/http-spans/ . If i look the several code generation at some point the directory http and net start to deasepear in the opentelemtry-go repo. I am not a go developer but happy to help if i can do something to restore this. |
The evolution of semantic conventions is managed here: https://github.com/open-telemetry/semantic-conventions They have made breaking changes in many of their subsequent releases. We package release version within their own Go package. Please refer to the appropriate |
I'm going to close this as it seems like the issue here is a misunderstanding about the upstream semantic convention stability policy and how that is implemented in the Go project. If you find an issue where one of our |
@aygalinc heads up, the semconv package linked from open-telemetry/opentelemetry-collector-contrib#31255 is not the same as https://pkg.go.dev/go.opentelemetry.io/otel/semconv |
Oh sorry i Mixed the packagé when i navigate |
Hi!
It seems that go semver is not consistent with the otel semver spécification.
As example, semver in version 1.21.0 does not contain the breaking change on http label due to the alignement with ECS spec.
It is a problem because exporter in otel contrib lib rely on this so actually on our system the exporter IS not able to do the mapping btw appinsight field and otel label.
The text was updated successfully, but these errors were encountered: