Hi,
On Grafana 7, when I had multiple stat panels for multiple data sources and a total panel for all of them, the sparkle graph max would adjust in each panel to the max of the data source. In Grafana 10, the max on all the panels seems to be set to the same value as the Total panel.
Grafana 7:
Grafana 10:
Is there any way to get Grafana 7-like functionality in Grafana 10? I can manually override with a static value, but I would like to be dynamic. Maybe there is a way to edit the JSON and to set the max to the max of the dataset in the override?
Thank you in advance for the help!
Tim
Hello,
I have Grafana 10.3.1 installed and I’m experiencing the v7 behavior according to what you exposed, but using Heatmap visualization. This is: I’m seeing independent Max values for every panel repetition.
But in my case, I need ‘your’ v10 behavior for my heatmaps, I mean, I need heatmap colors do match among all panel repetitions, and they actually don’t.
May this depend on the selected visualization? Did you finally find any parameter to switch from one to the other behavior?
Hi, I guess the main difference is in the number of panels - OP had (most probably) one panel, therefore the “global” max value (@tstonis if you’re still looking for an answer, try toggling Field min/max option).
In your case, you’re talking about repetition - I guess you’re using panel’s Repeat for option. Unfortunately, I’m not sure if you can set dynamic max across multiple panels - for instance, one query might end up with error, so how would you decide what the max is? You could either set static value or make a second query (in each panel) that would yield max of every queries and then set the value as Max through Config from query transformation.
Thank you for the suggestion, I will give it a try when I get a moment. Would be great to upgrade to a later version as I have stayed on v7 due to this issue!
If you’re going to upgrade, remember that alerting underwent total redesing in v8, so it might not be as straightforward 
Thank you so much for the suggestion, toggling the Field min/max option fixed this issue. I don’t know how I missed that option in the past.
It’s quite possible that this option wasn’t available (I don’t remember exactly when it was implemented though 
)
