4.8 (477) In stock
What's wrong? If an http.remote contains credentials, and the connection failed on start. then whole module with all properties are visible in the log which can cause a credentials leak Steps to reproduce Setup an Grafana Agent Flow and
Upgrade from 9.3.1 to 9.3.11, 9.4.9, or 9.5.1 fails on updating alert configuration and/or secret migration · Issue #67316 · grafana/grafana · GitHub
Alert rules -> unexpected error when doin anything in the query window · Issue #63401 · grafana/grafana · GitHub
grafana-sdk/custom-types_test.go at master · sourcegraph/grafana-sdk · GitHub
Opencost not supported when using a custom secret · Issue #285 · grafana/k8s-monitoring-helm · GitHub
Global secrets normalization · Issue #5946 · grafana/agent · GitHub
Sending Wrong data while alerting · Issue #16246 · grafana/grafana · GitHub
Grafana loki grafana-agent-test-0 Privileged container is not allowed · Issue #1928 · grafana/agent · GitHub
Alerting: Alert rules whose folder does not exist are effectively invisible in the Provisioning group API · Issue #69512 · grafana/grafana · GitHub
Error on Problems Panel · Issue #1021 · grafana/grafana-zabbix · GitHub
error fetching chunks & failed to get s3 object · Issue #5221 · grafana/loki · GitHub