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

Align graph panels with legend in table mode #1786

Closed
torkelo opened this issue Apr 15, 2015 · 6 comments
Closed

Align graph panels with legend in table mode #1786

torkelo opened this issue Apr 15, 2015 · 6 comments

Comments

@torkelo
Copy link
Member

torkelo commented Apr 15, 2015

Graph panels that use legend in table mode could often get panels that did not align:

image

This was due to the fact that when calculating the height of the graph canvas area only a single row legend is assumed. With this issue the legend height calculation will include the table header and ALL rows. So when using the legend in table mode the are reserved for the canvas graph will be reduced, so in order to restore the look you had for dashboards in v1.9 you need to increase the height for the Row.

After change:
image

This change not only does it align panels, it also solves this issue: #1749

@dutchiechris
Copy link

I loaded 2.0.1 and horror, ugliness! I use templates heavily and often have a varying amount of items to graph depending on the choice of some template item. A simple example is a template item "top resources" which then shows the top X metrics in panels. So the autosizing on overflow (old behavior) worked well; I would set the row height to the minimum I wanted it, put panels in a row that would all grow by the same count of graph items, and then if needed the rows would show with a greater height ensuring the graph was always visible.

Example of top 1:
image

And then top 4, as in 2.0.1:
image

Or previous to 2.0.1:
image

Any ideas on how I can workaround when my # of items to graph varies? Or a code change/feature that could accomodate when a user wants 'fixed' or 'minimum + autosize' heights?

Especially when using templates [that will result in variable metric counts] I think many users will hit issues with this change.

@torkelo
Copy link
Member Author

torkelo commented Apr 21, 2015

You can change the row height so that you can see the graph even with a lot of series. I can understand that some edge cases this change can cause problems. Will listen to feedback and see if a work around or new option is required.

Btw, on a other note, I see you are showing "max" and "avg" legend values at the same time for the same series. You know this can be misleading? That max and avg cannot be totally accurate at the same time? It depends on how your query looks and what aggregation is used to reduce the number of data points.

@lagndoy
Copy link

lagndoy commented Apr 21, 2015

Is there a new issue to track this? We have the same issue and our templating will result in 1 to 20+ records. This makes having to change the row height to accommodate for it, very inefficient. Workaround would be to not use a table in the legend but the table is just so much cleaner, it's used in about every graph/dashboard. I wouldn't say that this is an edge case.

@torkelo
Copy link
Member Author

torkelo commented Apr 22, 2015

@lagndoy there are already 3 issues that have reported that problem, and lucky for you it is already solved in #1832 (comment)

Will release a patch release 2.0.2 later today to tomorrow, in the mean time there are nightly builds with the fix here: http://grafana.org/download/builds (version is the 2.0.2-pre1)

@dutchiechris
Copy link

Tested using nightly build and my existing dashboards with metric count that varies and works for me. Thanks!

@torkelo
Copy link
Member Author

torkelo commented Apr 22, 2015

thats great

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants