Aaron Steinfeld

Can you elaborate? What's not working? This screenshot looks to be on the trace list of an endpoint rather than explorer (although they work more or less the same way)....

It's the implemented behavior for all filters (if the filter is left in an incomplete/invalid state, it's left that way to be finished later), but agree the UX isn't great....

As discussed offline, before even testing cytoscape - how does it affect the bundle size? If we're adding multiple MBs of libs to switch layout providers, then this approach doesn't...

Very curious on use case here

Could you please propose a design on this? Given that there's no current user preference persistence, this may not be a good fit for work until prerequisites are put in...

> This is my suggestion. By default, current time durations will be there, As an option Users can load their custom configuration from a file (JSON or something else). It...

> as a session-long upload by a particular user That seems like a pretty rough user experience - at that point, wouldn't the user be just as well configuring a...

> You are suggesting edit for individual time ranges and persist any changes locally. right? sounds good I'm suggesting some work arounds that seem no more difficult than loading up...

So the use case described by @suddendust is significantly different - instead of per user, its per tenant. Easy enough to do at build time (for all tenants across a...

So there's really a few places where config can happen: - At build time, when producing the docker image. This is more or less equivalent to a source code change/fork...