-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[APM] Service Inventory: Ensure perf improvements don't hurt UX #125789
Comments
what does it mean to "hide" services beyond "maxNumServices"? how will the customer access these? |
Pinging @elastic/apm-ui (Team:apm) |
The idea is that users would have to sort by a dimension (throughput, response time, error rate) or apply a filter (environment or kql search bar) to specify which services they want to see. |
In my mind I split this discussion into two experiences: Default view (when user opens services inventory):
Today, we provide ability to perform those via:
Secondary actions (which use will perform on the services inventory page):
Searching for a services could be via pagination or a search bar. Suggested next steps Here is what I suggest to consider:
|
My suggestion would be:
With this approach, I think we will have:
|
I can totally see the problem. If a customer knows they have 999 services, and we only show 50 without any explanation, they'll wonder where the remaining 949 are. However, this is already a limitation in the product today. The limit is just much higher (500) so fewer customers are hitting this limit today than if we lower it to 50.
Although I haven't looked into whether it's possible to lazy load data with EUI tables I expect this to be possible, yes. Another option we could consider is replacing the pagination with a "Load more" button.
Replacing the advanced kuery bar with a simple filter bar (for service name) makes even more sense when we launch service groups where the search bar filters on service group name: I really hope we can make a decision for 8.2 🤞 As a rule of thumb, I think there should always be a filter bar above tables with high cardinality data to filter on the primary name (eg. table of containers / hosts / pods). This will make it easier for users to find what they need if they know the name (or a subset of it) and will improve perf because we don't feel we have to show everything up front. |
The change was reverted back and merged into main #126325. The maximum number is back to 500 🥳 |
This issue is no longer needed:
|
In #125646 we reduced the number of services displayed on the inventory page from 500 to 50. This should improve performance for customers with many services but will hide services outside top 50.
We need to make sure this doesn't impact the UX too much. Some ideas:
@alex-fedotyev @formgeist
The text was updated successfully, but these errors were encountered: