[bug] Parent context not set in kafka consume and process message async helper

[padzikm]

Component

OpenTelemetry.Instrumentation.ConfluentKafka

Package Version

all version 1.15.*

Runtime Version

.net10

Description

Activity created for handling kafka message doesn't keep context passed from kafka message. Reason - parent context is set to default instead of extracted context from propagation context - https://github.com/open-telemetry/opentelemetry-dotnet-contrib/blob/main/src/OpenTelemetry.Instrumentation.ConfluentKafka/OpenTelemetryConsumeResultExtensions.cs#L143

Steps to Reproduce

Instrumented kafka consumer and using ConsumeAndProcessMessageAsync helper method to consume message - https://github.com/open-telemetry/opentelemetry-dotnet-contrib/blob/main/src/OpenTelemetry.Instrumentation.ConfluentKafka/OpenTelemetryConsumeResultExtensions.cs#L73

Expected Result

Created activity should have trace id the same as passed in traceparent kafka message header

Actual Result

Created activity has different trace id than passed in traceparent kafka message header

Additional Context

No response

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}

[Kielek]

I think that there is no bug here. See https://github.com/open-telemetry/opentelemetry-dotnet-contrib/blob/main/src/OpenTelemetry.Instrumentation.ConfluentKafka/OpenTelemetryConsumeResultExtensions.cs#L139-L141 and semantic-convention 1.24.0 https://github.com/open-telemetry/semantic-conventions/blob/v1.24.0/docs/messaging/messaging-spans.md

As long as we are not switching to the modern version there is nothing to change.
Please create new issues to track progress, if you are interested in on supporting supporting simultaneously new and old standards. More about this, you can read in important section under https://github.com/open-telemetry/semantic-conventions/blob/v1.40.0/docs/messaging/messaging-spans.md

[padzikm]

From above link for 1.24.0 semantic convention there is only mention about consumer links - 'For each message it accounts for, the "Deliver" or "Receive" span SHOULD link to the message's creation context.' but nothing about not correlating context, so I think it is missing piece to correlate traces from consumer to producer trace