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

Support display/visualization of data response status in the UI · Issue #58637 · grafana/grafana · GitHub

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

Grafana failed to load its application files with Apache reverse proxy · Issue #65642 · grafana/grafana · GitHub

Grafana proxy queries timeout after 30s with dataproxy.timeout and dataproxy.keep_alive_seconds to > 30s · Issue #35505 · grafana/grafana · GitHub

Error 502 randomly thrown when querying any datasource · Issue #20096 · grafana/grafana · GitHub

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

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

Upgrade from 8.2.1 to 8.3.1 caused all Grafana alert rules to lose all their query-type expressions due to data source not found and requires the manual recreation of ALL alert rules ·

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

Handle unsuccessful request · grafana grafana-json-datasource · Discussion #259 · GitHub

api/ds/query (QueryMetricsV2) should return more informative status code on query failure · grafana grafana · Discussion #40444 · GitHub