-
Notifications
You must be signed in to change notification settings - Fork 67
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
Fix layout issue in instance dashboard #543
Conversation
LGTM :) |
I think two more rows need to be updated(https://github.com/rhobs/configuration/pull/542) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome!
Maybe we should fix the faulty panels upstream? It would still be nice to be able to define our own layout...
Signed-off-by: Vibhu Prashar <[email protected]>
Updated Dashboard |
Initially, I also thought to fix this upstream but if everyone else is using why didn't they face the similar layout problem which we did? Is it because we use a different Grafana version or is it something related to our environment? I am still not clear on this that's why I didn't touch upstream. But yes if this is a genuine case then we should update upstream as well |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
I don't quite get how others upstream aren't affected by this. Maybe they fix it after import as well, or just copy over dashboard yaml and fix? In any case, would be great to have such a fix templated upstream
In thanos mixin builder.libsonnet we import grpc.libsonnet, http.libsonnet, slo.libsonnet and uses their functions like
httpQpsPanel
,httpErrPanel
,latencyPanel
etc for creating respective panels in our libsonnet. Since these function's don't have the property to change the span size and without that, they pick up the default values from this. It's best to remove the span property completely as it interferes with the default layout sizing which grafana provides as removing the span property allows grafana to dynamically size the panels inside a row.Link to dashboard using generated JSON