zipkin
zipkin copied to clipboard
Use "newest" as default sort for zipkin-ui
Currently the zipkin-ui uses "Longest first " as default sort method.While I usually found that "newest" is used more frequently. So , let's vote: Which one do you prefer as an zipkin fan? [A]Newest first [B]Longest first @adriancole
[A]
[A]
[A]
[A] according to the time series
a week and no screams for the other order and no alternatives mentioned. Switching and if someone yells, we'll know A wasn't unanimous
heh seems I smoked out a [B] from @basvanbeek
Typically the amount of spans happening in production make it so that newest first has little value. Inspecting slow paths is more likely. In dev newest first is preferable
I certainly agree that newest first is nice when you have very little data..
How about a compromise? Use LocalStorage, or some such mechanism, to persist it. So once I change it, it stays the way I want it for my use case. Which is [A] ;)
We can use config property I think. There are existing config properties for UI. @Logic-32 want to give a try?
Lol, I actually have been wanting to add LocalStorage/a cookie to the front-end to persist that setting for awhile. I probably wouldn't do a config property for it personally. But if I get any free time back I'll certainly take a stab. God knows that won't be until after the Zipkin2 UI goes out though :(
[A] for me, though I agree that it depends After starting the new environment I just want to see my test calls coming in and how long they take. Once it is running, I would like [B] to catch the longest one. Maybe indeed an extra 'keep this setting' is nice.
@Logic-32 hopefully I can take some heavy lifting off. if you want to just attack this one, would be appreciated (the stickiness)
Wondering if we shouldn't change the default in the mean time.. it is an optimization question until sticky.. do we make it more difficult for existing users or new ones. Currently it is more difficult for new users and that not only annoys them but likely adds support pressure one way or another.
Let's do Newest with a cookie in Lens. In the "notable" section of to be written docs about lens vs classic, we should mention that newest has disadvantages mentioned here.
Current behavior in Lens is that it resets to "Duration descending" i.e. "Newest first" each time you click on the Query button. This is a bit annoying. @tacigar seems like low hanging fruit for a 10x UI champ like you ;-)