We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I found a bug, not just asking a question, which should be created in GitHub Discussions.
I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.
I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.
Ubuntu
branch: develop
OpenJDK 1.8
The context created in telemetry does not include the custom headers set by interceptors.
Starting a client connect to proxy.
Expect contains custom headers like RPC_NAME in context.
Three is not custom headers like RPC_NAME in context.
No response
The text was updated successfully, but these errors were encountered:
[ISSUE apache#6964] use the correct context in telemetry; polish the …
78e21b3
…code structure
[ISSUE #6964] use the correct context in telemetry; polish the code s…
bbbe737
…tructure (#6965)
Successfully merging a pull request may close this issue.
Before Creating the Bug Report
I found a bug, not just asking a question, which should be created in GitHub Discussions.
I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.
I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.
Runtime platform environment
Ubuntu
RocketMQ version
branch: develop
JDK Version
OpenJDK 1.8
Describe the Bug
The context created in telemetry does not include the custom headers set by interceptors.
Steps to Reproduce
Starting a client connect to proxy.
What Did You Expect to See?
Expect contains custom headers like RPC_NAME in context.
What Did You See Instead?
Three is not custom headers like RPC_NAME in context.
Additional Context
No response
The text was updated successfully, but these errors were encountered: