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

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

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

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

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

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

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

Grafana dashboard shows too many outstanding requests after upgrade to v2.4.2 · Issue #5123 · grafana/loki · 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

malformed HTTP status code · Issue #11 · grafana/grafana-image-renderer · 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