incorrect status code returned by Grafana when prom data source returns throttling error (429) · Issue #48384 · grafana/grafana · GitHub
Descrição
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
api/ds/query (QueryMetricsV2) should return more informative status code on query failure · grafana grafana · Discussion #40444 · GitHub
incorrect status code returned by Grafana when prom data source returns throttling error (429) · Issue #48384 · 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
Inappropriate HTTP Status code received: Receiving 500 status code instead of 429 · Issue #73209 · grafana/grafana · GitHub
Getting 403 forbidden error when adding data source by IP - Prometheus - Grafana Labs Community Forums
Datasource proxy returning too many outstanding requests · Issue #4613 · grafana/loki · GitHub
Unable to add Loki datasource in grafana · Issue #1872 · grafana/loki · GitHub
Nginx 403 forbidden on static files using link_secure with grafana - Server Fault
Grafana dashboard shows too many outstanding requests after upgrade to v2.4.2 · Issue #5123 · grafana/loki · GitHub
de
por adulto (o preço varia de acordo com o tamanho do grupo)
