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

Handle unsuccessful request · grafana grafana-json-datasource · Discussion #259 · 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

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

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

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

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

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

Problem Grafana · Issue #29 · sni/grafana-pnp-datasource · GitHub