Simplify search on specific tags

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

We’ve identified a few tags that are frequently used as a search criteria in Jaeger and would like to make it simpler to search on it.

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

Searching by Tags requires the tag name in addition to the value. There’s no way to “lock” a specific tag that is widely used

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

It would be nice if we could provide the Query component with a list of tags that would always be shown. Something like this:

A future version of this could be based on the selected service with a default for everyone (similar to the adaptive sampling config)

Any open questions to address

N/A

Might be related to https://github.com/jaegertracing/jaeger-ui/issues/235

[yurishkuro]

@jkowall there are 5 upvotes, summarily closing may not be the best approach.

I do agree with you that this feels like a very specific feature that will be a maintenance burden without much benefit. In particular, in a large enough installation/organization who decides which tags should be elevated to such special status?

I can see a different version of this that could be more useful - a history-based helper. The top text box will remain the generic multi-tag entry, and below it a new section

You used these tags previously [tag1] [tag2] [tag3]

where [tagN] are pills with tag names and clicking on appends tagN= back to the single multi-entry box and puts cursor right after it with focus.

[yurishkuro]

I don’t think auto-completion would work here because it would remember the whole query, and I expect queries to differ while often using similar tags.

Browsers have local storage, I was thinking of that rather than cookies or server side.