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

¯\_(ツ)_/¯ is not very clear #129

Closed
Dieterbe opened this issue Nov 29, 2017 · 7 comments
Closed

¯\_(ツ)_/¯ is not very clear #129

Dieterbe opened this issue Nov 29, 2017 · 7 comments

Comments

@Dieterbe
Copy link

hut-waeuaoeuaoeue

this is kindof neat (I know i have a problem with character encoding not rendering the shrugging person very well), but it would be nice if this could also somehow indicate why it's showing the shruggy thing, i'm probably missing a field in my traces, maybe it could explain me what's missing, via a little popup, or link to a faq entry or something

@yurishkuro
Copy link
Member

Is that a tooltip? I have no idea what it means.

@Dieterbe
Copy link
Author

it's a tooltip when you hover over traces in the timeline visualisation on top of the search results

@tiffon
Copy link
Member

tiffon commented Nov 29, 2017

#117 should do away with it.

It indicates, sometimes erroneously, that the root trace is unknown and therefore the name of the trace is TBD.

@yurishkuro
Copy link
Member

regardless of #117, if the UI cannot determine the "name" of the trace, it should show a better string than the shrug emoticon, like "cannot find trace name".

@Dieterbe
Copy link
Author

FWIW I run into this despite having an all-jaeger stack, which doesn't seem to jive with #117
also don't know if relevant here but I sometimes notice that my search results have "roots" that are actually supposed to be leaves. eg some operations halfway through processing. as if somehow some of the spans got lost. is that possible? I guess most likely some of the spans didn't make it through the pipeline correctly (maybe timeouts between agents and collector?)

@yurishkuro
Copy link
Member

it's also possible that due to timing the query is picking up incomplete traces.

@tiffon
Copy link
Member

tiffon commented Dec 16, 2017

Fixed by #134.

@tiffon tiffon closed this as completed Dec 16, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants