Igor Sirotin afe90a9d31
chore(metrics): sync fleet dashboards from Grafana (#4079)
Refreshed the two shared-Grafana dashboards and re-applied the old-or-new metric
name union from #4074, so the panels keep working across the rename.

  waku-fleet-dashboard.json         v181 -> v191
    drops the five deprecated Store v2 panels; the "Store V3 Times wire-to-wire"
    query moves to sum without (phase) and changes() instead of deriv(), which is
    the better staleness filter for a gauge that moves and returns
  waku-single-node-dashboard.json   v7 -> v9
    no functional change, a Grafana 12 re-save (pluginVersion, threshold base,
    schemaVersion 40 -> 41)

The $dc variable is populated from libp2p_peers rather than waku_version as the
export had it: libp2p_* comes from a dependency and is immune to our renames, so
it cannot rot the next time metrics are renamed. Grafana keeps variable queries
outside `expr`, so the #4074 union pass never saw this one.

Store/Archive is collapsed again, matching the other rows; the export had it open
because of whoever last hit save. "Store v3 query request rates" moves to x=0 to
fill the space left by deleting its v2 sibling.

The dashboards under apps/ are deliberately not synced. They are provisioned into
the docker-compose stacks that ship beside them (docker-compose.yml mounts
monitoring/configuration/dashboards into /var/lib/grafana/dashboards), so they
must match the local datasources.yaml and prometheus-config.yml, not status.prod.
The Grafana copies carry a datasource uid that the local stack does not provision
and job selectors that its single scrape job cannot match.
2026-07-30 16:42:39 +01:00
..