lair/quantus
2
0
Fork 0
Code Issues 4 Pull Requests Actions Packages Projects Releases Wiki Activity

fix: ship the grafana dashboard provider, and assert it loaded
deploy / fetch (push) Successful in 17s
Details
deploy / deploy-node (bob.hanzalova.internal, 0x134e73f06fa9bdb1dbfa909e149c563f5860ceb71a0e7307918f7033970edf59, benjy.hanzalova.internal, --public-addr /dns4/nh.thgttg.com/tcp/30333) (push) Successful in 30s
Details
deploy / deploy-miner (1, benjy.hanzalova.internal, bob.hanzalova.internal) (push) Successful in 43s
Details
deploy / deploy-metrics (push) Failing after 10s
Details

Browse Source 
The dashboard JSON was deployed but its provider config never was, so
Grafana had no reason to read the directory -- the dashboard would have
been a file on disk and an empty folder in the UI.

Tracked separately from the dashboard because Grafana reads providers
only at container startup while dashboards are re-read on the
provisioning interval: a provider change restarts grafana, a dashboard
change does not.

validate now queries Grafana's search API for the dashboard uid rather
than testing that a file exists, since a provisioned dashboard that
fails to parse leaves the JSON looking perfectly fine on disk.
This commit is contained in:
Rob Thijssen
2026-08-31 18:46:14 +03:00
parent 6e931842dd
commit 2c896ed618
2 changed files with 31 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
script/infra-setup.sh
+2
View File
@@ -271,6 +271,8 @@ PROM
cat > "$tmp" <<'SUDO'
gitea_ci ALL=(root) NOPASSWD: /usr/bin/rsync * /etc/prometheus/scrape_configs.d/quantus.yml
gitea_ci ALL=(root) NOPASSWD: /usr/bin/rsync * /etc/grafana/provisioning/dashboards/quantus/quantus.json
gitea_ci ALL=(root) NOPASSWD: /usr/bin/rsync * /etc/grafana/provisioning/dashboards/quantus-dashboards.yaml
gitea_ci ALL=(root) NOPASSWD: /usr/bin/systemctl restart grafana.service
SUDO
chmod 0440 "$tmp"
visudo -cf "$tmp"