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 end to end distributed tracing with Alloy #2521

Open
sarita-maersk opened this issue Jan 24, 2025 · 0 comments
Open

Support end to end distributed tracing with Alloy #2521

sarita-maersk opened this issue Jan 24, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@sarita-maersk
Copy link

Request

Enable distributed tracing where the request flow starts from Alloy and continues to downstream services. I’ve already enabled Alloy’s meta-monitoring with the tracing block and can see Alloy's traces, but I’m unsure if it’s possible to enable distributed tracing and set Traceparent header or something similar which will get propagated to downstream services. Could anyone guide me on this?

tracing {
 sampling_fraction = 0.1
 write_to         = [otelcol.processor.attributes.default.input]
}

Use case

Support Traceparent header in Alloy self tracing.

@sarita-maersk sarita-maersk added the enhancement New feature or request label Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant