-
What Grafana version and what operating system are you using?
One instance is kubernetes grafana oss 10.0.1 and other is Windows Server grafana oss 11.1.0 -
What are you trying to achieve?
So, in the Kubernetes grafana the time range picker is absolute. If you put a timeline in your query (azure monitor) this gets ignored. Which is very nice, because then users can choose their own time range in the built in grafana function, rather than setting up custom variables.
In the brand new Grafana instance I’ve set up this is not the case. We haven’t configured this in either of the setups, it just arrived with a new Grafana version at some point.
-
How are you trying to achieve it?
I’ve looked at the time range section in config, but none the wiser. -
What did you expect to happen?
I expected the built in time range picker to function in our new grafana instance as it does with the “old” one.