inbuxa/inbuxa-admin
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 22 Wiki Activity Sponsor

Dashboard: read gauges per node #76

Merged
jcoffey-dev merged 2 commits from fix/gauges-per-node into main 2026-10-01 02:01:46 +00:00
Conversation 0 Commits 2 Files Changed 5
+119 -17
2 Commits
Author SHA1 Message Date
jcoffey-dev 229dd6179d Dashboard: write the underflowed test readings as expressions
ci / build (pull_request) Skipped
Details
ci / publish (pull_request) Skipped
Details
github/ci (branch) GitHub Actions
Details
ci / github (pull_request) Successful in 1m42s
Details 
no-loss-of-precision rejected the 20-digit literals.
 2026-09-30 18:59:39 -07:00
jcoffey-dev cbff590d49 Dashboard: read gauges per node
github/ci (branch) GitHub Actions
Details
ci / build (pull_request) Skipped
Details
ci / publish (pull_request) Skipped
Details
ci / github (pull_request) Failing after 1m2s
Details 
Every node stores its own gauge readings, and the dashboard took the
latest from whichever node wrote last, or added up every reading in a
chart slice. Per-node gauges (memory, open connections) showed one node
or a pile of ticks, and the cluster-wide counts could show another
node's drifted copy: a 20-digit queue (an underflow stored unsigned) or
0 accounts.

gaugeReading takes each node's latest reading, adds per-node gauges up,
and for queue/user/domain counts takes the largest believable one, which
also skips the junk already in history (inbuxa-server stops storing it).
Cards, chart slices and the memory tile use it; the tile now reads all
nodes from history rather than one node's live value.
 2026-09-30 18:52:56 -07:00