-
Notifications
You must be signed in to change notification settings - Fork 8k
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
[Dataset quality] Services and Host limits #181579
Comments
Pinging @elastic/obs-ux-logs-team (Team:obs-ux-logs) |
As users will not be able to see the full hosts / service list here, I wonder if we could just use an indicator for the number. If the number is low <10, we might show the exact number. If the number is >10, we just show > 10 and user can jump to the host / service page to get the precise answer. This could also help with performance potentially. Side note: I'm thinking of a similar approach to docs count and degraded docs. As soon as we have large numbers, do we need the exact cound or would be |
I don't think users would expect to customize the number of results they see, so I would exclude the Hosts approach, which feels a bit more like a pagination setting. I'm ok with having ranges or being approximative as ruflin suggests, as long as I am able to click on it and get the full list of results that should be fine. |
Is the docs count we have there at the moment total or degraded? It would be nice to have both (15/10k), 1%, but could we combine it into one box? |
@ruflin i think for now the metric is absolute. i'll look into having both separated |
In the flyout summary we limited the number of services and hosts we are "discovering" from logs.
Currently the limit is set to
50
for both, services and hosts.❓ Open questions
The text was updated successfully, but these errors were encountered: