-
Notifications
You must be signed in to change notification settings - Fork 203
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
Propagating Context #120
Comments
This is because the RedisClient interface (https://github.com/adjust/rmq/blob/master/redis_client.go) was created at a time when the Redis library wasn't context aware. So we would need to update the interface, the implementations and callers. What would we want to use the contexts for here, though? |
@wellle for me: I would like to trace Redis calls to better understand the application performance. (OpenTelemetry) Also, it would be great if rmq would have tracing built in (similar to the redis client). |
For tracing please have a look at #136. |
Closing as tracing as supported now. |
Looking in this file:
https://github.com/adjust/rmq/blob/master/redis_wrapper.go#L10-L74
Why is there logic that actively prevents context from being passed to the redis commands? Any issue with exposing additional logic that has all these functions, but just
Ctx
at the end of the name to pass context?The text was updated successfully, but these errors were encountered: