-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Migrate to latest semconv version and ensure we regularly update going forward #22095
Comments
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 Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
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 Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
We can do this in two steps: first we update until 1.20.0, then we deal with the HTTP semantic conventions upgrade |
Hello! I’m interested in taking on this issue as my first contribution to OpenTelemetry. I see it’s labeled as a 'good first issue,' and I’d love to get started. Please let me know your thoughts. |
@narcis96 You can pick a component from the following list:
and update all imports that refer to |
thanks ! will do that. |
**Description:** The version of semconv is upgraded from to v1.6.1 to v1.27.0 **Link to tracking Issue:** #22095 **Testing:** Tests passed
Description: The version of semconv is upgraded from v1.6.1 to v1.27.0 Link to tracking Issue: #22095 Testing: Tests passed
…ry#35273) Description: The version of semconv is upgraded from v1.6.1 to v1.27.0 Link to tracking Issue: open-telemetry#22095 Testing: Tests passed
…ry#35341) Description: The version of semconv is upgraded from v1.6.1 to v1.27.0 This is a trivial migration. semconv usage inside component: - conventions.AttributeServiceName="service.name" on both versions Link to tracking Issue: open-telemetry#22095 Testing: Tests passed
Description: The version of semconv is upgraded from v1.6.1 to v1.27.0 This is a trivial upgrade because only the test file has been modified. The semconv attributes' value have been compared using [go-otel-semconv-comparator](https://github.com/narcis96/go-otel-semconv-comparator) resulting in 0 diffs. Link to tracking Issue: open-telemetry#22095 Testing: Tests passed
Description: The version of semconv is upgraded from v1.18.0 to v1.27.0 This is a trivial upgrade. The semconv attributes' value have been compared using [go-otel-semconv-comparator](https://github.com/narcis96/go-otel-semconv-comparator). All attributes used by this component have the same value in both versions. Link to tracking Issue: open-telemetry#22095 Testing: Tests passed
…5269) Description: The version of semconv is upgraded from to v1.17.0 and v1.5.0 to v1.27.0 Link to tracking Issue: open-telemetry#22095 Testing: Tests passed Co-authored-by: Alex Boten <[email protected]>
…35315) Description: The version of semconv is upgraded from v1.6.1 to v1.27.0 Link to tracking Issue: open-telemetry#22095 Testing: Tests passed
…ry#35272) Description: The version of semconv is upgraded from v1.6.1 to v1.27.0 Link to tracking Issue: open-telemetry#22095 Testing: Tests passed
…try#35271) Description: The version of semconv is upgraded from v1.13.0 and v1.9.0 to v1.25.0 Link to tracking Issue: open-telemetry#22095 Testing: Tests passed
Description: The version of semconv is upgraded from to v1.6.1 to v1.27.0 Link to tracking Issue: open-telemetry#22095 Testing: Tests passed
…n-telemetry#35392) Description: The version of semconv is upgraded from v1.6.1 to v1.27.0 This is a trivial upgrade. The semconv attributes' value have been compared using [go-otel-semconv-comparator](https://github.com/narcis96/go-otel-semconv-comparator). All attributes used by this component have the same value in both versions. Link to tracking Issue: open-telemetry#22095 Testing: Tests passed
…5391) Description: The version of semconv is upgraded from v1.6.1 to v1.27.0 This is a trivial upgrade. The semconv attributes' value have been compared using [go-otel-semconv-comparator](https://github.com/narcis96/go-otel-semconv-comparator). All attributes used by this component have the same value in both versions. Link to tracking Issue: open-telemetry#22095 Testing: Tests passed
Description: The version of semconv is upgraded from to v1.6.1 to v1.27.0 The semconv attributes' value have been compared using [go-otel-semconv-comparator](https://github.com/narcis96/go-otel-semconv-comparator) resulting in relevant 0 diffs. Link to tracking Issue: open-telemetry#22095 Testing: Tests passed
Description: The version of semconv is upgraded from v1.6.1 to v1.18.0 This is a trivial upgrade. The semconv attributes' value have been compared using [go-otel-semconv-comparator](https://github.com/narcis96/go-otel-semconv-comparator). All attributes used by this component have the same value in both versions. Link to tracking Issue: open-telemetry#22095 Testing: Tests passed
Description: The version of semconv is upgraded from v1.6.1 to v1.27.0 This is a trivial upgrade because only the test file has been modified. The semconv attributes' value have been compared using [go-otel-semconv-comparator](https://github.com/narcis96/go-otel-semconv-comparator) resulting in 0 diffs. Link to tracking Issue: open-telemetry#22095 Testing: Tests passed
) Description: The version of semconv is upgraded from v1.6.1 to v1.26.0 This is a trivial upgrade. The semconv attributes' value have been compared using [go-otel-semconv-comparator](https://github.com/narcis96/go-otel-semconv-comparator). All attributes used by this component have the same value in both versions. Link to tracking Issue: open-telemetry#22095 Testing: Tests passed
…try#35368) Description: The version of semconv is upgraded from v1.6.1 and v1.9.0 to v1.27.0 This is a trivial upgrade. The semconv attributes' value have been compared using [go-otel-semconv-comparator](https://github.com/narcis96/go-otel-semconv-comparator) resulting in 0 diffs. Link to tracking Issue: open-telemetry#22095 Testing: Tests passed
…ry#35350) Description: The version of semconv is upgraded from v1.6.1 to newer versions The semconv attributes' value have been compared using [go-otel-semconv-comparator](https://github.com/narcis96/go-otel-semconv-comparator) resulting in 0 diffs: - 1.7.0 version has been used if the no newer version contains all attributes used by the file (all attributes of 1.6.1 exists and have the same value inside 1.7.0) - 1.12.0 version has been used if the no newer version contains all attributes used by the file (all attributes of 1.6.1 exists and have the same value inside 1.12.0) - 1.27.0 version has been used if only if the file does _not_ contain _AttributeMessagingMessageID_ and _AttributeMessagingKafkaMessageKey_: <img width="798" alt="otel_comp" src="https://github.com/user-attachments/assets/5e9befc7-80f9-4758-a357-0dec82373a11"> Link to tracking Issue: open-telemetry#22095 Testing: Tests passed
Description: The version of semconv is upgraded from v1.6.1 to v1.27.0 This is a trivial migration. semconv usage inside component: - conventions.AttributeServiceName="service.name" on both versions - conventions.AttributeServiceNamespace="service.namespace" on both versions Link to tracking Issue: open-telemetry#22095 Testing: Tests passed
) Description: The version of semconv is upgraded from v1.6.1 to v1.12.0 This is a trivial migration. The semconv attributes' value have been compared using [go-otel-semconv-comparator](https://github.com/narcis96/go-otel-semconv-comparator) resulting in 0 diffs: - all attributes of 1.6.1 exists and have the same value inside 1.12.0 Link to tracking Issue: open-telemetry#22095 Testing: Tests passed
…y#35270) Description: The version of semconv is upgraded from v1.6.1 and v1.18.0 to v1.27.0 Link to tracking Issue: open-telemetry#22095 Testing: Tests passed
…#35355) Description: The version of semconv is upgraded from v1.18.0 to v1.27.0 This is a trivial migration. The semconv attributes' value have been compared using [go-otel-semconv-comparator](https://github.com/narcis96/go-otel-semconv-comparator) resulting in 0 diffs (all attributes of 1.18.0 exists with the same value inside 1.27.0) Link to tracking Issue: open-telemetry#22095 Testing: Tests passed
Description: The version of semconv is upgraded from v1.6.1 to newer versions This upgrade is trivial. The semconv attributes' value have been compared using [go-otel-semconv-comparator](https://github.com/narcis96/go-otel-semconv-comparator) resulting in 0 (relevant) diffs: - conventions.AttributeServiceName="service.name" on both versions Link to tracking Issue: open-telemetry#22095 Testing: Tests passed
Description: The version of semconv is upgraded from v1.6.1 to v1.12.0 Link to tracking Issue: open-telemetry#22095 Testing: Tests passed
Description: The version of semconv is upgraded to v1.27.0 The semconv attributes' value have been compared using [go-otel-semconv-comparator](https://github.com/narcis96/go-otel-semconv-comparator) resulting in 0 diffs: - 1.12.0 version has been used if the no newer version contains all attributes used by the file (all attributes of 1.6.1 exists and have the same value inside 1.12.0) - 1.27.0 version has been used if only if the file does not contain AttributeMessagingMessageID and AttributeMessagingKafkaMessageKey: Link to tracking Issue: #22095 Testing: Tests passed
…35241) Description: The version of semconv is upgraded to v1.27.0 The semconv attributes' value have been compared using [go-otel-semconv-comparator](https://github.com/narcis96/go-otel-semconv-comparator) resulting in 0 diffs: - 1.12.0 version has been used if the no newer version contains all attributes used by the file (all attributes of 1.6.1 exists and have the same value inside 1.12.0) - 1.27.0 version has been used if only if the file does not contain AttributeMessagingMessageID and AttributeMessagingKafkaMessageKey: Link to tracking Issue: open-telemetry#22095 Testing: Tests passed
Description: The version of semconv is upgraded from v1.13.0 to v1.27.0 This is a trivial upgrade. The semconv attributes' value have been compared using [go-otel-semconv-comparator](https://github.com/narcis96/go-otel-semconv-comparator). All attributes used by this component have the same value in both versions. Link to tracking Issue: #22095 Testing: Tests passed
) Description: The version of semconv is upgraded from v1.6.1 to v1.21.0 This is a trivial upgrade. The semconv attributes' value have been compared using [go-otel-semconv-comparator](https://github.com/narcis96/go-otel-semconv-comparator). All attributes used by this component have the same value in both versions. Link to tracking Issue: #22095 Testing: Tests passed
Description: The version of semconv is upgraded from v1.6.1 to v1.27.0 This is a trivial upgrade. The semconv attributes' value have been compared using [go-otel-semconv-comparator](https://github.com/narcis96/go-otel-semconv-comparator). All attributes used by this component have the same value in both versions. Link to tracking Issue: #22095 Testing: Tests passed
Description: The version of semconv is upgraded from v1.6.1 to v1.18.0 This is a trivial upgrade. The semconv attributes' value have been compared using [go-otel-semconv-comparator](https://github.com/narcis96/go-otel-semconv-comparator). All attributes used by this component have the same value in both versions. Link to tracking Issue: #22095 Testing: Tests passed
Description: The version of semconv is upgraded from v1.6.1 to v1.18.0 This is a trivial upgrade. The semconv attributes' value have been compared using [go-otel-semconv-comparator](https://github.com/narcis96/go-otel-semconv-comparator). All attributes used by this component have the same value in both versions. Link to tracking Issue: open-telemetry#22095 Testing: Tests passed
Component(s)
No response
Describe the issue you're reporting
As highlighted by @sumo-drosiek on #18740 (comment), we use a lot of different versions of
go.opentelemetry.io/collector/semconv
across this repository.We would want to:
For the latter, I am not sure what is the best way to do this; one option is to have an internal package that re-exports symbols from a fixed semconv package and just update this one. This package could be autogenerated to keep it updated.
The text was updated successfully, but these errors were encountered: