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
Grafana 8 variables stopped working due to the HTTP method change #45817
Comments
can you show the raw response from
Any errors in the browser dev console? If you are running Grafana behind a reverse proxy, you need to make sure that you are passing the original Host and Origin headers from the client request to Grafana.
|
Providing additional info:
|
Grafana 9 has a heavily rewritten Prometheus backend and Grafana 8 isn't supported for non-critical issues anymore, if this is still a problem in Grafana 9, please open a new issue for that. |
We've switched to Grafana 9.1.2 and the issue does not reproduce 😸 |
What happened:
Background
We are trying to migrate from Grafana 7.5.13 to 8.4.1 in our k8s cluster (deployed via official Grafana helm chart).
We have a bunch of dashboards already defined for cluster monitoring and they are relying on dynamic variables obtained via Prometheus queries.
Problem
Once we swap the image to Grafana 8, dynamic variables are not working due to the lack of response from datasource proxy.
One of the cases - we need to have variable obtained via prom query:
In grafana 7 variable queries used
GET
and it worked OK on our cluster:In grafana 8 variable queries seem to be using
POST
:For some reason this
POST
hangs indefinitely without responseWhat you expected to happen:
POST https://<grafana8>/api/datasources/proxy/1/api/v1/series
sent from Grafana UI receives response and allows configuring dynamic PromQL variables.I would like to get some guidance how to debug this further, or how to reconfigure Grafana to use legacy
GET
(if possible).GET
when querying variable values?How to reproduce it (as minimally and precisely as possible):
Not sure if this is reproducible outside of our setup. I assume if that would be common issue it would've been already posted.
Anything else we need to know?:
We use envoy proxy in every pod (including grafana & prometheus), because we use Istio service mesh on the cluster.
Initial debug from our end:
inside
promehteus-server
container (bothcurl
-s work OK):inside
grafana
container (all belowwget
-s work OK, returning valid prometeus API payloads):Environment:
bitnami/prometheus:2.31.2
grafana/grafana8.4.1
docker imageThe text was updated successfully, but these errors were encountered: