-
Notifications
You must be signed in to change notification settings - Fork 37
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
Change mininum and maximum percentage for graphs in dashboards #1782
Comments
@Hardikl Could you check this. |
Thanks @faguayot! The advantage of the current behavior is small % differences are more obvious. Extending the range from 0 to 1 "flattens" some values and makes it harder to spot minor changes. Of course, that advantage can also be considered a con. I agree that the defaults should probably be fixed between 0 and 1. We'll investigate and get back to you. |
Soft min and max may be a way to improve this, although for most of our
|
@cgrinds Thanks for you quick answer. I understand what you say about small % differences, and it makes sense. I guess depending on the situation could help use the minimum 0 and maximum 100 (or 1 depending on the scale) or not. When I look for something
|
hi @faguayot if you want to try these out before the next release, you can grab the latest nightly build. |
Verified on 3ffa2eb |
Describe the bug
Define the minimum and maximum in the percentage graphs since we can't have a right vision of the use of any value due to we are not painting the minimum to 0% and the maxixum which should be 100% in most of cases.
Environment
Provide accurate information about the environment to help us reproduce the issue.
Expected behavior
Actual behavior
Additional context
It is recomment to review all dashboards, since I have seen the same situation in differents.
The text was updated successfully, but these errors were encountered: