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
Kafka plugin, multiple consumer issue, UI/spanId related. #7212
Comments
The web side got these logs.
|
The config for the kafka plugin:
|
hi @yjqg6666 In my guessing, this is probably due to that Queue is a virtual node. This is my guess, and the exact problem seems to need analysis. thanks :) |
@koo-taejin thanks for the quick reply. How about the second one? The pSpanID may came from the kafka header and used for three different applications. I think it's a hard-to-solve issue. How about replace with new spanIds on the web side? |
@yjqg6666 Thanks for your reporting |
@koo-taejin Should i keep this issue open or close it. |
@yjqg6666 thanks :) |
@koo-taejin Hopefully there would be a better official solution for the queue type(one-to-many). |
Thank you so much for giving me a great idea. If it is possible, could you send me your work to PR? thanks :) |
@koo-taejin I just sent a PR. |
In the PR, the web side contains some specific code for Kafka-only, it's not a good solution. There should be a better /general solution for the queues. |
I let you know progression of this issue. I am looking to solve problem 1. The cause seems to be the wrong EndPoint. There seems to be a problem with trying to handle it well without EndPoint, because it was too difficult to get the correct EndPoint with Stably. I am thinking of getting EndPoint at Kafka Selector. So, If I find out good solution, then I will commit it. thanks :) |
@koo-taejin I am building the master now and will check and update soon. |
@koo-taejin Checked and have confirmed that the first issue is fixed. Thumb up! The topic-publish app: The topic-consume app: The topic-publish app(inbound-1 and outbound-2): |
I am glad to hear that. If I have any progression, then I am going to share with you. thanks :) |
Can you check the issue 2 using the master branch? As a result of analysis, it is expected that the information of callerHost has been changed due to the changed endPoint, so it will come out normally. If the results come out, please share thanks :) |
checking. |
@koo-taejin not working. It should be: |
@yjqg6666 |
@yjqg6666 |
@koo-taejin It's fixed in the main server map. Now the issue only exist in the server map for a single transaction and only if the consumer apps both/all call the same other app. |
I have understood that what you mean. |
I let you know progression of this issue 2. I have found out reason of this issue and the way I solve this issue. thanks :) |
checking. |
@koo-taejin Now it works like a charm. |
@yjqg6666 Please close this issue, If you do not have any problem. thanks :) |
Prerequisites
What version of pinpoint are you using?
2.0.4
Describe the bug
When one app send a kafka message triggered by a http request, multiple apps consume the same message and process the message, then these apps make another http request to a http service. The whole thing could be described as the following server map (two outbounds).
issue 1:
The main server map could not show correctly(the consumer node could be omitted or linked) when one outbound is chosen as the screenshot below.
issue 2:
The app consumer-verify1, consumer-verify2 and consumer-verify3 each called verify-http-server-dev. They all should be linked to the verify-http-server-dev node and the call counts should be 1 for each.
The server map for this transaction should look like the following:
The request headers:
verify1 -> http-server
verify2 -> http-server
verify3 -> http-server
They all had the same Pinpoint-pSpanID but got different Pinpoint-pAppName. The Pinpoint-pSpanIDs should be different.
The text was updated successfully, but these errors were encountered: