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

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

Problem Grafana · Issue #29 · sni/grafana-pnp-datasource · 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

ingestion rate limit exceeded · Issue #1923 · 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

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

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

Save dashboard failure and pop up a 403 forbidden alert · Issue #24082 · grafana/grafana · GitHub

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

Cannot add Loki as a Prometheus datasource for alerting · Issue #6313 · grafana/loki · GitHub

Cannot add Loki as a Prometheus datasource for alerting · Issue #6313 · grafana/loki · GitHub