You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The application is a small service running in Kubernetes with a standalone installation of Redis and Jaeger besides Kubernetes. The service is able to communicate with Redis and Jaeger, but the combination of both via redisotel does not work.
Detailed Description
Jaeger does not receive any traces from redis operations.
I can take the TraceProvider in the example, create a Tracer from it and send a trace to Jaeger with no problems, but it does not work with redisotel.
Both the configuration of the TraceProvider via redisotel.WithTracerProvider() and otel.SetTracerProvider() does not work.
The text was updated successfully, but these errors were encountered:
@cmergenthaler No, I have not. I remember that I took a look at the sources, but it's been some time and I can't remember if I had found anything of value.
I'm currently working in a different project but I'll notify my colleagues that the issue might be fixed with the next version of go-redis. Thanks for the update!
Expected Behavior
My application should send a trace to Jaeger.
Current Behavior
Nothing happens. No error in the log, no crash of the app, no trace in Jaeger.
Steps to Reproduce
Context (Environment)
The application is a small service running in Kubernetes with a standalone installation of Redis and Jaeger besides Kubernetes. The service is able to communicate with Redis and Jaeger, but the combination of both via redisotel does not work.
Detailed Description
Jaeger does not receive any traces from redis operations.
I can take the TraceProvider in the example, create a Tracer from it and send a trace to Jaeger with no problems, but it does not work with redisotel.
Both the configuration of the TraceProvider via
redisotel.WithTracerProvider()
andotel.SetTracerProvider()
does not work.The text was updated successfully, but these errors were encountered: