-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Not all the spans rendered in the ui #3428
Comments
We see the same thing. I'm pretty sure it's a bug. But I'm not so sure it will be fixed since the activity level in this project is really low :/ |
Any news on this issue? I am still facing the same bug with the latest version. Is there a fix/workaround for this? |
I have the same issue as well. |
We have same Issue. |
@seet61 @anujva |
I was able to fix this. For the issue was the parent span was not being saved, which is why only the spans which had a parent were being rendered. Once I fixed the issue of the saving of the span, the UI started rendering them correctly. |
Cc @tacigar
…On Mon, 9 Jan 2023, 05:48 Dmitry Arefyev, ***@***.***> wrote:
@Rathan-Naik <https://github.com/Rathan-Naik> example
bb587ff076de11edb650005056b0c457 (2).zip
<https://github.com/openzipkin/zipkin/files/10370404/bb587ff076de11edb650005056b0c457.2.zip>
—
Reply to this email directly, view it on GitHub
<#3428 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAXOYAUEEMZ4TYV6KHUJQT3WROKBTANCNFSM5NRAZFMA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Describe the Bug
Hi, I'm not sure if this is a bug or a mis-configuration, I have the following json coming from some spring cloud services and the rendering seems to be missing some spans, the service named main-integration-unit is always not visible, even though it's present in the JSON, can you help me on understanding why or if it's a bug, should we re-open this case?
The Json:
Steps to Reproduce
Expected Behaviour
All spans included in the Json rendered in the UI
The text was updated successfully, but these errors were encountered: