Open MiriamAparicio opened 1 year ago
Pinging @elastic/apm-ui (Team:APM)
Question for the refinement: I would expect, that because we already have the filters on the top, the filters on the table work differently, for example to be able to filter more than one row at the same time, but if we filter as the Instances table, the table we will filter out just the selected row
cc @akhileshpok @boriskirov
I believe all the filters we use on APM, affects the URL which means the top level filters. With Unified Search, we can either update the search bar with the selected filter from the table or add Pills, in either case, we will have to update the URL.
If we don't want to update the main search bar, we can create Pills like this
Pills sounds like a good solution for ad-hoc filters.
If we already have a dedicated control (dropdown) we might want to update that instead of a adding a pill. This way we won't have the same dimension represented twice. However this does increase complexity.
Follow up from https://github.com/elastic/kibana/issues/146877
Add the filters to the tables, so the user can filter the table.
It should work similar to the filters we have for Instances, where we update the search bar.
Questions