Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support W3C Trace Context and the traceparent header #54

Open
wadearnold opened this issue Jan 23, 2024 · 2 comments
Open

Support W3C Trace Context and the traceparent header #54

wadearnold opened this issue Jan 23, 2024 · 2 comments
Assignees
Milestone

Comments

@wadearnold
Copy link
Collaborator

The http client should be able to support the W3C trace context and traceparent header. The library should receive and updated trace from the Moov services. Users of the SDK that are already using open telemetry in their application should have the go/sdk append their traces to ctx

# {version}-{trace_id}-{span_id}-{trace_flags}
traceparent: 00-80e1afed08e019fc1110464cfa66635c-7a085853722dc6d2-01
    client := http.Client{
        // Wrap the Transport with one that starts a span and injects the span context
        // into the outbound request headers.
        Transport: otelhttp.NewTransport(http.DefaultTransport),
        Timeout:   10 * time.Second,
    }

We should write an advanced readme for how to use distributed tracing in the moov-go sdk

@adamdecaf
Copy link
Member

Is the W3 trace spec compatible with Open Tracing? I didn't think the two worked together.

@wadearnold
Copy link
Collaborator Author

It is supported by open telemetry
https://github.com/open-telemetry/opentelemetry-go

@adamdecaf adamdecaf added this to the v0.3.0 milestone May 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants