-
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
[UX] Core web vitals should have empty state #79419
Comments
Pinging @elastic/uptime (Team:uptime) |
Pinging @elastic/apm-ui (Team:apm) |
Agreed, this is misleading. As well as some kind of inactive/greyed out web vital bars (so as not to suggest that 100% of users have had a poor experience). cc @formgeist |
I'd assume "N/A" is better than 0 ms or any of the other values. Secondly, yes we should have an empty state "No data available" on the stacked bar visualization. Perhaps a light grey background with the text on top which keeps the component in view but without the confusing data. Lastly, I wanted to point out that there's a loading indicator on the values, but not on the stacked bar visualization. Perhaps a small spinner like the graph spinner would be a good addition as well for those loading states. It's similar to what we use on the sparklines in the other panels. |
Kibana version:
When no data is selected core web vitals displays this state , it should have empty state, possibly in grayed out bars.
The text was updated successfully, but these errors were encountered: