incorrect status code returned by Grafana when prom data source returns throttling error (429) · Issue #48384 · grafana/grafana · GitHub

What happened: When Prometheus data source returns a throttling response (status code: 429) for a query, it is converted to a 400 status code by Grafana server. Also, the error message returned by data source is eaten up by Grafana serve

Datasource proxy returning too many outstanding requests · Issue #4613 · grafana/loki · GitHub

Datasource proxy returning too many outstanding requests · Issue #4613 · grafana/loki · GitHub

Grafana dashboard shows too many outstanding requests after upgrade to v2.4.2 · Issue #5123 · grafana/loki · GitHub

Inappropriate HTTP Status code received: Receiving 500 status code instead of 429 · Issue #73209 · grafana/grafana · GitHub

Problem Grafana · Issue #29 · sni/grafana-pnp-datasource · GitHub

incorrect status code returned by Grafana when prom data source returns throttling error (429) · Issue #48384 · grafana/grafana · GitHub

Grafana panel throws Unknown Error During Query Transaction when the value All is selected · Issue #47159 · grafana/grafana · GitHub

Grafana dashboard shows too many outstanding requests after upgrade to v2.4.2 · Issue #5123 · grafana/loki · GitHub

Grafana fails to start when trying to provision a single datasource to be deleted · Issue #44243 · grafana/grafana · GitHub