How does OTel Collector handle Http semantic convention breaking changes in v1.23.0

[wangzlei]

Context:

• https://opentelemetry.io/blog/2023/http-conventions-declared-stable/
• https://www.honeycomb.io/blog/opentelemetry-http-attributes

From Dec 2023, language SDKs such as java, .Net, have removed environment variable OTEL_SEMCONV_STABILITY_OPT_IN support. The latest version of OTel SDK only emit the new http attributes. So, some vendors got customer issue that http attribute fields missing.

• Update to latest semantic conventions #29687
• Http semantic convention breaking changes in 1.23 #30935

From the otel collector code I suppose the semantic convention in Collector is still v1.22.0? May I know is there plan for migrating the http semantic convention breaking change? If there is no plan, should I manually update my exporter translation logic to be:

import conventions "go.opentelemetry.io/collector/semconv/v1.6.1"

span.Attributes().Range(func(key string, value pcommon.Value) bool {
		switch key {
		case conventions.AttributeHTTPMethod, "http.request.method":  // http.request.method is new attribute key 
			translate to vendor's span format...