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

Unable to add Loki datasource in grafana · Issue #1872 · grafana/loki · GitHub

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

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

429 too many outstanding requests occurred even when there're only few requests · Issue #2315 · grafana/tempo · GitHub

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

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

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

HTTP Error Bad Request · Issue #167 · grafana/simple-json-datasource · GitHub

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

Error message not forwarded when listing resources in ConfigEditor · Issue #141 · grafana/athena-datasource · GitHub

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

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