Go semconv seems not be consistent with otel semconv spec

open-telemetry / opentelemetry-collector

OpenTelemetry Collector

https://opentelemetry.io

Apache License 2.0

4.34k stars 1.44k forks source link

Go semconv seems not be consistent with otel semconv spec #9592

Closed aygalinc closed 2 months ago

aygalinc commented 7 months ago

Describe the bug Starting with the semconv 1.21.0, info in trace resource seems to not correspond to semantic convention. As example all info related to http is missing, is it intended ?

I see that exporter-contrib are base on the generated semconv, so basically if trace that follow semantic convention in version > 1.20 is ingested some exporter failed to map field to trace store. We use the azuremonitor in our production system and it is not usable anymore.

aygalinc commented 7 months ago

Link to : https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/31255

codeboten commented 2 months ago

thanks for reporting this @aygalinc, as of the merge of v1.25.0, the generated_attribute_group.go includes the http semconv. Please re-open if that doesn't solve the issue