-
Notifications
You must be signed in to change notification settings - Fork 913
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
Alibaba latest Rocket MQ cannot be auto-instrumented. #6741
Comments
@sweetxiaodai @laurit I'll fix it. |
It was done? @aaron-ai awesome |
I am working on it. Related pull request will be created recently, thanks for your attention! |
@sweetxiaodai , thanks for you attention. This feature has been merged, and you could use it in next release, related issue: #6884 #7019 |
I'll close this issue, since it's implemented now. If you run into any further issues, please reopen or open a new one. |
Describe the bug
A clear and concise description of what the bug is.
Alibaba released their latest RocketMQ v5.0 meanwhile it published its client maven dependencies. However, the otel-
java-auto-instrumentation cannot capture the trace if we use the following client libraries.
Official SDK for public
If you use Alibaba cloud RocketMQ PaaS service, it also provide you with a all-in-one SDK. This also cannot be auto-instrumented by the javaagent.
Steps to reproduce
If possible, provide a recipe for reproducing the error.
Use above SDK connect to RocketMQ, and start the jar with javaagent. Observe in jaeger, you cannot find the span and trace.
What did you expect to see?
A clear and concise description of what you expected to see.
Capture produce and consume trace.
What did you see instead?
A clear and concise description of what you saw instead.
What version are you using?
v18.0
Environment
Compiler: OracleJDK1.8
OS: Ubuntu 20.04, MacOS
Runtime "Oracle JRE 8u251"
OS: MacOS
Additional context
Add any other context about the problem here.
contact me if you want to have a short discussion.
The text was updated successfully, but these errors were encountered: