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

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

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

ingestion rate limit exceeded · Issue #1923 · grafana/loki · GitHub

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

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

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

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

too many outstanding requests on v2.4.2 · Issue #5851 · grafana/loki · GitHub

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

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

Failed to Add Data Source: HTTP Error Bad Gateway · Issue #295 · Altinity/clickhouse-grafana · GitHub

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

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

Prometheus: No error returned when response_limit is hit with /ds/query · Issue #73747 · grafana/grafana · GitHub