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

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 #48384 · grafana/grafana · GitHub

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

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

Login and/or Redirect Issue with Grafana & AzureAD Single Sign On -- login.OAuthLogin(missing saved state) · Issue #30259 · grafana/grafana · GitHub

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

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

Getting 403 forbidden error when adding data source by IP - Prometheus - Grafana Labs Community Forums

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

NetworkError when attemting to fetch resource -> Unexpected error with more then 10 queries · Issue #46268 · grafana/grafana · GitHub

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

Datasource: show descriptive errors when response isn't JSON · Issue #50465 · grafana/grafana · GitHub

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