It seems silly that we are unable to dynamically assign limits via SQL queries / questions in an application that is designed to display SQL data. Having to hard-code these values makes these gauges significantly less useful
3 Likes
I couldn't see anything on GitHub that would help, you could add your own issue as a feature request.
For anyone else, here's the equivalent in MS PowerBI:
The dashboard allows you to select a property or all, number of bookings and number of available rooms both come from SQL.
Only workaround is to do percentages up to 100.
There’s a couple of issues about this - more or less the same - upvote by clicking 
on the first post of each:
https://github.com/metabase/metabase/issues/6514
https://github.com/metabase/metabase/issues/4412
I feel the same way here, Adoria. I can only understand the fixed values in the gauge working in very simple and specific situations, with none of the dynamism that is normally common in the business world. One way I tended to use Gauge was, instead of showing absolute values, I presented percentages, and then configured colors for each percentage. Let's say, 50% of the target would be yellow, regardless of what the absolute value is. But showing a percentage doesn't make sense for the user, they want to know the absolute value of that information. I could show that on other cards, but then it consumes precious screen space, in addition to forcing the user to navigate their eyes and interpret more information, which loses the agility of interpretation necessary in a dashboard.