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

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

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

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

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

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

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

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

malformed HTTP status code · Issue #11 · grafana/grafana-image-renderer · GitHub

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

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

Grafana proxy queries timeout after 30s with dataproxy.timeout and dataproxy.keep_alive_seconds to > 30s · Issue #35505 · grafana/grafana · 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 ·