-
Notifications
You must be signed in to change notification settings - Fork 12
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
Only fixed sizing for radar graphs available since 1.4.3 #11
Comments
hotstepper13
changed the title
Only fixed sizing for radard graphs available since 1.4.3
Only fixed sizing for radar graphs available since 1.4.3
Apr 15, 2019
Agreed, will try to have a look next week end. |
Thank you. I have had already a look but i have no clue how this works in order to make a sufficient fix. |
Done cheers, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Entry Criteria:
My plan is to use radar style graphs for Infra Monitoring in terms of having specific values for multiple servers on one graph. This allows judging by observing the "shape" of the drawn figure. If the value from one server will raise, the "shape" is no longer "symmetric" allowing to see issues very fast.
Within the last release the option of defining min and max values for the graph were introduced.
After this you are forced to set a min and a max value for the graph and avoiding the automatic extension of the graph to the current max value.
Description:
I have a radar graph that should show the current active thread count for four tomcat instances. All instances are currently around 160 Threads. Using the 1.4.2 provided by grafana plugin repository, the lower values cannot be seen as the graph is chosing to size from the min to the max (mean in the area between 156 to 162) which means the minimal values are located in the center.
With the new version from master (direct download) the graph is preconfigured with min=0 and max=0 which results a completely colored field as all values are above 0. By setting the max value to 200 everything looks as expected.
BUT, as our tomcats might use up to 1000 Threads there might be situations where the value is out of the scale.
Removing the value for max, inserting 0 for min and having a step of 0 render the are from -0.5 to 0.5. Adding a step of 10 breaks the whole view.
Expectation:
Removing a value for min, max or step should default to "auto" like in other grafana graph´s
The text was updated successfully, but these errors were encountered: