Skip to content
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

A way to indicate which Summary values are not aggregated by the time range #39308

Open
igoristic opened this issue Jun 19, 2019 · 4 comments
Open
Labels
discuss enhancement New value added to drive a business result Team:Monitoring Stack Monitoring team Team:Platform-Design Team Label for Kibana Design Team. Support the Analyze group of plugins.

Comments

@igoristic
Copy link
Contributor

Sometimes users assume that the top-right time range picker (in Stack Monitoring > Overview) is applied to all data points on the UI.

This is true for Monitoring charts, but not true for most (if not all) Summary values:
Screen Shot 2019-06-19 at 4 40 20 PM

Couple of proposed solutions:

  • Including an (i) info icon next to each value which will say if a number is aggregated or not and maybe a little more info about the context/calculation of the final displayed value
  • Re-word the labels to emphasis total eg: "Total Events Received"
@igoristic igoristic added discuss Team:Platform-Design Team Label for Kibana Design Team. Support the Analyze group of plugins. enhancement New value added to drive a business result Team:Monitoring Stack Monitoring team labels Jun 19, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-design

@elasticmachine
Copy link
Contributor

Pinging @elastic/stack-monitoring

@cchaos
Copy link
Contributor

cchaos commented Jun 19, 2019

@igoristic Since you're not using the full filter/query bar alongside the date/time picker. Would it make sense just to remove the global version and piece in that component into the panel containing the charts that the time picker is associated with?

Screen Shot 2019-06-19 at 17 34 39 PM

@ycombinator
Copy link
Contributor

If all Summary Bar metrics across all Stack Monitoring views where the Summary Bar is shown don't use the time picker range, then I think @cchaos's suggestion would work really well. So perhaps we should audit all such metrics first?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss enhancement New value added to drive a business result Team:Monitoring Stack Monitoring team Team:Platform-Design Team Label for Kibana Design Team. Support the Analyze group of plugins.
Projects
None yet
Development

No branches or pull requests

4 participants