HTTP Client Span父Span丢失求助：请求成功时出现孤立Span

问题现象 #

应用配置OpenTelemetry链路追踪后出现异常：

• HTTP请求失败时，父Span可正确关联至HTTP客户端Span，追踪表现符合预期
• 请求成功时，HTTP客户端Span变为无关联的孤立Span，同时出现**"无效父Span ID"**警告

相关代码 #

HTTP客户端初始化代码 #

transport := traceHttp.NewTracedTransport(nil, otel.GetTracerProvider())
httpClient:= http.Client{Transport: transport}

自定义链路追踪工具库代码 #

package http

import (
    "context"
    "net/http"
    "net/http/httptrace"

    "go.opentelemetry.io/contrib/instrumentation/net/http/httptrace/otelhttptrace"
    "go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp"
    "go.opentelemetry.io/otel/trace"
)

func NewTracedTransport(transport http.RoundTripper, provider trace.TracerProvider) *otelhttp.Transport {
    if transport == nil {
        transport = http.DefaultTransport
    }
    return otelhttp.NewTransport(
        transport,
        otelhttp.WithClientTrace(func(ctx context.Context) *httptrace.ClientTrace {
            return otelhttptrace.NewClientTrace(ctx)
        }), 
        otelhttp.WithTracerProvider(provider), 
        otelhttp.WithSpanNameFormatter(name),
    )
}

func name(_ string, req *http.Request) string {
    return "HTTP " + req.Method + " " + req.URL.Path
}

问题原因 #

otelhttp.Transport本身已内置对httptrace的OpenTelemetry集成支持，无需手动通过WithClientTrace添加otelhttptrace.NewClientTrace。手动添加该配置会导致请求流程中出现两次Span上下文处理：

• 请求失败时，错误流程终止了其中一方的Span创建，父关联不受影响
• 请求成功时，两个trace组件的上下文发生冲突，父Span ID被错误覆盖或丢失，最终出现孤立Span和"无效父Span ID"警告

解决步骤 #

修改NewTracedTransport函数，移除otelhttp.WithClientTrace配置项：

func NewTracedTransport(transport http.RoundTripper, provider trace.TracerProvider) *otelhttp.Transport {
    if transport == nil {
        transport = http.DefaultTransport
    }
    return otelhttp.NewTransport(
        transport,
        otelhttp.WithTracerProvider(provider), 
        otelhttp.WithSpanNameFormatter(name),
    )
}

验证效果 #

修改后重新运行应用：

• 请求成功时，HTTP客户端Span可正确关联至父Span
• "无效父Span ID"警告不再出现

内容的提问来源于stack exchange，提问作者dhia Gharsallaoui