Skip to content

Ensure trace context is propagated from incoming and to outgoing requests #129

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

Open
gaelreyrol opened this issue Jan 28, 2025 · 3 comments

Comments

@gaelreyrol
Copy link
Contributor

We need to ensure trace context is propagated from incoming requests to current instrumentation and to outgoing requests.

@AtCliffUnderline
Copy link

@gaelreyrol hello! Sorry for bothering, but is it already works, or something should be done for trace to be propagated from incoming request? Maybe not understand ensure correctly :)
Having some troubles with it for now, so want to help if it is not works.

@AtCliffUnderline
Copy link

@gaelreyrol
Copy link
Contributor Author

Hi @AtCliffUnderline, I created this issue like a reminder that something needs to be done about this.

Currently, it does not work and it needs to be implemented in two parts:

From an incoming request, I need to collect trace context to reuse the trace id instead of creating a new one.
On an outgoing request, add trace context to allow another service to reuse it.

You will find documentation here: https://opentelemetry.io/docs/languages/php/propagation/.

It should be done by following the W3C Trace Context Recommendation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants