It works on Grafana 11.0 and below, so it looks like a recent change.
Could it be caused by this PR ?
DISCLAIMER: With Flux, I couldn’t figure out how to get a Query-type variable to work, seemingly because Flux expects time bounds (|> range(start: v.timeRangeStart, stop: v.timeRangeStop)), and dashboard query variables don’t appear to support that. So the Flux-derived panels instead use Custom-type variables.
grafana:main ← grafana:ismail/introduce-custom-variable-support
opened 11:42AM - 15 May 24 UTC
**What is this feature?**
In general variable queries are just strings. But w… e need more flexibility to support various scenarios. To achieve that we need custom variable support. In this PR I am just implementing the custom variable support and not changing any logic.
This will help us to handle/deliver this https://github.com/grafana/grafana/issues/84120
**Why do we need this feature?**
More flexibility in the variable editor
**Who is this feature for?**
InfluxDB users
### How to test
- Have Influxql, Flux and SQL variables in legacy support.
- Switch to this branch and test them again, try to run, refresh, update.
- Introduce a new set of Influxql, Flux and SQL variables and save the dashboard.
- Refresh, view and edit.
- All actions must work.
2 Likes
