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

See "error" tag in UI multiple time #1470

Open
DavitSo opened this issue Apr 12, 2019 · 9 comments
Open

See "error" tag in UI multiple time #1470

DavitSo opened this issue Apr 12, 2019 · 9 comments

Comments

@DavitSo
Copy link

DavitSo commented Apr 12, 2019

Requirement - what kind of business use case are you trying to solve?

Problem - what in Jaeger blocks you from solving the requirement?

Proposal - what do you suggest to solve the problem or improve the existing situation?

Any open questions to address

@DavitSo
Copy link
Author

DavitSo commented Apr 12, 2019

I see "error" tag in UI multiple times in same span.

@objectiser
Copy link
Contributor

This could be fixed when converting the trace into json, by making sure the tags are unique (based on both name and value).

As it is only performed when retrieving an individual trace, the performance impact should be minimal.

Would you be interested in contributing a fix?

@DavitSo
Copy link
Author

DavitSo commented Apr 12, 2019

Now I can't take time to this.
In any case i'll be happy to help as much as I can.

@objectiser objectiser added the good first issue Good for beginners label Apr 12, 2019
@yurishkuro
Copy link
Member

My preference is to do minimum necessary amount of data cleanup in the backend, so that issues can actually be traced back to instrumentation. Here the double error tag is coming from instrumentation that does not follow OT conventions.

@yurishkuro
Copy link
Member

If we do implement deduping, we need to start persisting span warnings in the storage.

@objectiser
Copy link
Contributor

Here the double error tag is coming from instrumentation that does not follow OT conventions.

Not sure where the behaviour is defined for this situation? Plus multiple layers of instrumentation may potentially be recording tags/logs on the same span - however they have no way to query the span to retrieve a tag (e.g. to determine if error tag already set).

@yurishkuro
Copy link
Member

Not sure where the behaviour is defined for this situation?

The APIs say that the behavior is undefined in these cases and recommend not calling SetTag more than once for the same key.

Anyway, I do realize that this is confusing to the end user looking at the trace in the UI, so I think it's fine to dedupe on retrieval, and add a span warning about it. This way we don't need to change the storage layers to support span warnings. We may need some UI enhancements to enable visualizing of span warnings.

@yurishkuro yurishkuro removed the good first issue Good for beginners label Apr 13, 2019
@DavitSo
Copy link
Author

DavitSo commented Apr 29, 2019

Hi,
Any update ?

It would be ok if there will be way to check if with this key already set tag or not.

@rubenvp8510
Copy link
Contributor

I'm working on this one :)

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

4 participants