-
Notifications
You must be signed in to change notification settings - Fork 29
Add tracing with opentelemetry go sarama wrapper #179
Conversation
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.
Stupid question ... what does console tracing mean? Always when i used tracing in the past I was sending the traces for example to Jaeger.
the end goal usually is to use jaeger yes. |
Thanks for the explanation. I'm not sure how useful really the tracing into the file is on Kubernetes because it brings issues with storage etc. with it. So I wonder if we should target a full support to be able to ship the logs to Jaeger. @ppatierno WDYT? |
i making the change to target JAEGER if you are ok to integrate the tracing feature |
Adding tracing is definitely valuable, however I think it would be great if the tracing backend is configurable , maybe a |
I don't think that tracing to the console is something really useful, also bringing problems related to storage already mentioned by Jakub. |
Jaeger provides a zipkin compatible API, so typically it's a good strategy (as a first step) to target zipkin and it'd work for both |
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.
I certainly think tracing is a good idea for the canary.
Console tracing works for me as a proof of concept, but would need something else to actually go forward. I think the config-map approach suggested else where is a promising way to go.
i've just done the jaeger exporter |
is all good on this PR ? |
32a5f09
to
e5a1e42
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.
On the right track for me.
My only concern is how best to handle the exporter selection.
is all good ? |
@melchiormoulin could you fix the DCO and conflicts please? So that we can have another pass. Thanks! |
3183f82
to
56cc874
Compare
i can't easily do the DCO with the merge, can you help me ? |
@melchiormoulin I think we are going to make a 0.4.0 release out for the latest important bug fixes merged today. The release candidate could be out tomorrow. This PR still needs another pass from all reviewers and I was wondering if you thought about adding some tests. I think it will make 0.5.0 but it doesn't mean that it will be so late after 0.4.0. |
yes i can add some test but i wanted to be sure all people are ok with the current implementation. |
i added some tests |
can you just help me for dco ? the |
4131487
to
56cc874
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.
LGTM. Thanks for the 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.
@melchiormoulin sorry for the delay! I left a couple of more comments but then we should be ok on my side.
You should fix DCO and check why tests are failing.
Opentelemetry tracing with Jaeger or OTEL exporter configured by EXPORTER_TYPE_TRACING env variable Signed-off-by: Melchior Moulin <melchior.moulin@gmail.com>
@ppatierno seems good now |
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.
@melchiormoulin thank you very much! Sorry for this PR taking so long!
Adding tracing with opentelemetry sarama wrapper
Why ?
Add more telemetry data for debugging a particular message, more convenient than logs.
How ?
By putting this env variable ACTIVATE_TRACING=true
Here is just an example of a console tracing.
If this PR is accepted i can handle a more generic approach than the console exporter.