-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Restore jaegerthrifthttpexporter #5666
Restore jaegerthrifthttpexporter #5666
Conversation
/cc @jpkrohling |
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
24411a0
to
5e2cc3e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is looking great! There are a few helpers and changes to the config that we did over time that need to be applied here to be consistent with the other components. Let me know if you want me to handle those changes in a subsequent PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. @bogdandrutu, I think I caught all the "modernization" issues, but would you like to check it as well? Otherwise, we can always improve later.
@ctreatma, could you take a look at the build failures? Some things do seem related to this PR, like this:
Also, I'll run a manual e2e test and report back the results. |
Looks like there's something missing:
This is the config file I'm using:
|
dismissing the review until the manual tests succeed as well
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This PR is looking great! I did a manual e2e test, and it worked. There's a test still failing, though:
You also need to add the new module to the |
I updated a few places where I missed the |
An unrelated test failed (fluentbit receiver?). Sorry, I hit "re-run jobs" before I could copy the output to create an issue. |
Sorry, there was a release in between and the go.mod is now conflicting :/ Would you please rebase this? It is already approved and will be merged after resolving the conflict. |
In some cases, a Jaeger collector may be deployed to a platform that does not support gRPC. This restores the jaegerthrifthttpexporter so that OpenTelemetry users who need to ship traces to a Jaeger collector that cannot support gRPC are able to ship traces using the Jaeger collector's [Thrift over HTTP API](https://www.jaegertracing.io/docs/1.27/apis/#thrift-over-http-stable).
Co-authored-by: Juraci Paixão Kröhling <[email protected]>
This removes the protospan_to_jaegerthrift translator because we can use the existing internal_to_jaegerproto translator to translate from from internal spans to Jaeger domain spans. The Jaeger domain spans to Jaeger Thrift conversion is small enough that I think it makes more sense as part of the exporter now. That said, some tests may need to be added for the exporter to cover the code that used to be in protospan_to_jaegerthrift. I still need to convert from jaeger/model.Batch to thrift-gen/jaeger.Batch, which will require a separate translator
b5e31c5
to
acec9f0
Compare
Description:
In some cases, a Jaeger collector may be deployed to a platform that does not support gRPC. This restores the jaegerthrifthttpexporter so that OpenTelemetry users who need to ship traces to a Jaeger collector that cannot support gRPC are able to ship traces using the Jaeger collector's Thrift over HTTP API.
This also adds a warning to the
README
for the restored exporter directing users to use thejaeger
exporter instead ofjeager_thrift
if they are able to do so.Link to tracking Issue: #4667
Testing:
Documentation: