Jaeger: Search traces

[zoltanbedi]

What this PR does / why we need it:

This PR implements search query for Jaeger.

TODO

• Add images to docs
• Update UI once Nico is ready with his feedback
• Add tests

Which issue(s) this PR fixes:

Fixes #24953
Fixes #27245

[CLAassistant]

All committers have signed the CLA.

[achatterjee-grafana]

Added some review comments.

[achatterjee-grafana]

Another suggestion.

[achatterjee-grafana]

Added copy edit changes.

[achatterjee-grafana]

LGTM

[aocenas]

Code looks good but there are some behavior that I think we should try to fix:

1. The limit placeholder is not seen in full so it's not clear what it means, we should probably put longer description in some info tooltip.
   

2. When querying logs the order is not stable and I get random traces every time. This isn't happening in jaeger ui so I assume there is either some param in the API or they sort the traces by time after they get them.

3. There seems to be some weird behavior with min/max limits but some of that is also present in Jaeger. In Jaeger if I use both min + max it seems like max is ignored. In this PR it seems like max limit is always ignored.

[zoltanbedi]

Code looks good but there are some behavior that I think we should try to fix:

1. The limit placeholder is not seen in full so it's not clear what it means, we should probably put longer description in some info tooltip.
2. When querying logs the order is not stable and I get random traces every time. This isn't happening in jaeger ui so I assume there is either some param in the API or they sort the traces by time after they get them.
3. There seems to be some weird behavior with min/max limits but some of that is also present in Jaeger. In Jaeger if I use both min + max it seems like max is ignored. In this PR it seems like max limit is always ignored.

1. Added the placeholder text to the info tooltip instead.
2. It seems like that they sort by most recent traces so I changed it to do the same. Don't we have a field config related to sorting?
3. I couldn't reproduce this. I see the same behaviour as in the Jaeger UI.

[aocenas]

I couldn't reproduce this. I see the same behaviour as in the Jaeger UI.

hmm yes you are right, but still this seems super weird, I mean this seems like a bug in the Jaeger API but I think this will create some issues for us as people will assume it's a bug in Grafana. @hemdrup @davkal what do you think about this? From perspective of Grafana user this seems broken. Should we allow only one of mix/max at the time? Or some disclaimer?

Another small nitpick:
Would probably change the placeholder to something like foo, bar, baz (or some more real tags) to give an example of the syntax (delimiter) as that is more helpful there imho.

[thunderpigeon]

Should we allow only one of mix/max at the time? Or some disclaimer?

• @aocenas Great idea on the "tag" example
• @aocenas Not sure what you mean by "only one min/mac" Do you mean multiple allowing filters like? Show me logs between 2-3s + logs between 4-5s?

[aocenas]

@hemdrup I meant that right now if you filter 1ms - 2ms as min max duration you still get traces > 2ms. This bug is also seen in jaeger UI so probably not something we can fix on our side easily, but the thing is this will look like it's broken in Grafana. The limits work though if used separately so I was thinking we could just put a switch there so you can set only one at a time.

[aocenas]

We can check the min/max issue in later PR