-
Notifications
You must be signed in to change notification settings - Fork 192
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 for Jaeger Propagator #1187
Comments
I don't remember us ever having a jaeger propagator. We removed the jaeger exporter in #890 when the client libraries were abandoned, but that doesn't mean the propagator can't be implemented. It can go in the Extension dir alongside B3 and CloudTrace if you'd like to have a go at implementing. |
Thanks for the answer, I'll start working on it |
Merged
Merged
5 tasks
yurishkuro
pushed a commit
to open-telemetry/opentelemetry-specification
that referenced
this issue
Apr 11, 2024
## Changes Included in open-telemetry/opentelemetry-php#1187 For non-trivial changes, follow the [change proposal process](https://github.com/open-telemetry/opentelemetry-specification/blob/main/CONTRIBUTING.md#proposing-a-change). * [ ] Related issues # * [ ] Related [OTEP(s)](https://github.com/open-telemetry/oteps) # * [ ] Links to the prototypes (when adding or changing features) * [ ] [`CHANGELOG.md`](https://github.com/open-telemetry/opentelemetry-specification/blob/main/CHANGELOG.md) file updated for non-trivial changes * [x] [`spec-compliance-matrix.md`](https://github.com/open-telemetry/opentelemetry-specification/blob/main/spec-compliance-matrix.md) updated if necessary Co-authored-by: Carlos Alberto Cortez <[email protected]>
carlosalberto
added a commit
to carlosalberto/opentelemetry-specification
that referenced
this issue
Oct 31, 2024
## Changes Included in open-telemetry/opentelemetry-php#1187 For non-trivial changes, follow the [change proposal process](https://github.com/open-telemetry/opentelemetry-specification/blob/main/CONTRIBUTING.md#proposing-a-change). * [ ] Related issues # * [ ] Related [OTEP(s)](https://github.com/open-telemetry/oteps) # * [ ] Links to the prototypes (when adding or changing features) * [ ] [`CHANGELOG.md`](https://github.com/open-telemetry/opentelemetry-specification/blob/main/CHANGELOG.md) file updated for non-trivial changes * [x] [`spec-compliance-matrix.md`](https://github.com/open-telemetry/opentelemetry-specification/blob/main/spec-compliance-matrix.md) updated if necessary Co-authored-by: Carlos Alberto Cortez <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The OpenTelemetry specification suggests that a propagator for Jaeger MUST be implemented.
Is your feature request related to a problem?
Some applications, typically third party, rely on "older" implementations of Opentracing using the Jaeger tracing context and this information is not being linked to the current PHP library.
Describe the solution you'd like
Adding a propagator that implements, understands and propagate the Jaeger (uber header) format.
Additional context
If it really hasn't been implemented, I'd love to contribute a PR
The text was updated successfully, but these errors were encountered: