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 failed to load its application files with Apache reverse proxy · Issue #65642 · grafana/grafana · GitHub

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

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

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

Nginx 403 forbidden on static files using link_secure with grafana - Server Fault

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 ·

429 too many outstanding requests occurred even when there're only few requests · Issue #2315 · grafana/tempo · 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

Status code correction for client canceled requests in Grafana backend logs · Issue #46337 · grafana/grafana · GitHub