-
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
allow to show gauges in multiple lines #12716
Comments
i would suggest to use percentage mode if you plan to put multiple gauges together with any chart you can produce unusable results ... try to do a bar chart, date histogram on x axis then do a term split with 50 terms .... that won't make sense. or pie, or any other chart pretty much. its up to the user to figure out what still makes sense, and yeah i agree showing tens of gauges won't make sense in most scenarios. |
currently gauges can be shown either horizontally or vertically i updated the title of this issue, if i understand correctly what we are looking for is have a mix of two (horizontally positioned gauges in multiple lines) |
Yep, exactly - some adaptable layout that'll use the space more optimally (and as a side-effect allow the individual gauges to render larger) would be great. :) |
Kibana version:
5.5
Elasticsearch version:
5.5
Server OS version:
Mac OS
Browser version:
Chrome
Original install method (e.g. download page, yum, from source, etc.):
Download
Description of the problem including expected versus actual behavior:
When I try to make multiple gauges (5) the number cannot be displayed if it has more than 5 digits, including decimal points. This might be OK for simple counts of small data sets, but is unusable for real-world use.
For more terms it is even worse:
That is simply too few for practical use, as anything in the thousands is not visible. Consider that a second has more than a thousand miliseconds, making these impractical for very common time periods. Also, if you use any type of aggregation (average, median, etc.) you will definitely have lots of decimal points to content with.
You should automatically move the text below the gauge if there will be overlap.
Steps to reproduce:
The text was updated successfully, but these errors were encountered: