Skip to content
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

The distributed trace chain is broken when Redis is treated as a message queue #583

Closed
ascrutae opened this issue Nov 10, 2017 · 5 comments
Labels
TBD To be decided later, need more discussion or input.
Milestone

Comments

@ascrutae
Copy link
Member

ascrutae commented Nov 10, 2017

The trace context isn't propagate when Redis is treated as a message queue.

@ascrutae ascrutae added the TBD To be decided later, need more discussion or input. label Nov 10, 2017
@iHuangYaoshi
Copy link

This needs users to define a rule to mix traceId and queue message element, then write a plugin to parse the rule . but it is possible to prodcuce other problems.

@wu-sheng
Copy link
Member

wu-sheng commented Mar 4, 2018

@KaiwenWang Yes, that is why @ascrutae keeps it in TBD. Can't find a safe way to solve this.

@wu-sheng wu-sheng added this to the 8.2.0 milestone Sep 14, 2020
@wu-sheng
Copy link
Member

Close for now.

@zhangnew
Copy link

Is there a solution yet ?

@wu-sheng
Copy link
Member

Is there a solution yet ?

There is no good solution for this. We just opened this for backlog.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
TBD To be decided later, need more discussion or input.
Projects
None yet
Development

No branches or pull requests

4 participants