Http semantic convention breaking changes in 1.23

[wangzlei]

Component(s)

No response

What happened?

Description

http semantic convention 1.23.0 is declared as stable and introduces some attribute changes. For example, AttributeHTTPMethod is from http.method to http.request.method. Now most of language SDKs have moved to the latest http semantic convention and removed support environment variable OTEL_SEMCONV_STABILITY_OPT_IN.

Right now some vendors' exporter in Collector have translation logic like

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:  // only handle http.method, cannot handle http.request.method
			translate to vendor's span format...

If we cannot control what version of OTel SDK user is using, how does Collector ensure both forward and backward compatibility?

Steps to Reproduce

Expected Result

OTel Collector can handle both old and new version of SDK.

Actual Result

Collector version

0.93.0

Environment information

Environment

OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")

OpenTelemetry Collector configuration

No response

Log output

No response

Additional context

No response

[jsultana-leap]

Thanks so much for the quick PR to address this :) Can I ask roughly when the fix will be released in a new version?

[github-actions]

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 @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

[github-actions]

This issue has been closed as inactive because it has been stale for 120 days with no activity.