fix(metrics/ui): dnsdist backend state as a gauge + cleaner config tables #84
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/dns-traffic-state-gauge-ui"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fixes the "random up/down" (item #1)
Root cause: I'd made backend
statea metric label onoctet_dnsdist_backend_queries. Every state flip changed the series identity, so VictoriaMetrics kept both anupand adownseries (+ stale/duplicate variants), and the instant query returned all of them — the same backend showing up and down, andrate()resetting on each flip.Fix:
octet_dnsdist_backend_upgauge (1=up, 0=down), no state label; dropoctet_statefrom the counter so it's stable (clean QPS rate) and state is one clean series per backend.--charttokens, no raw palette), dimmed down-rows, and an "N/M up" summary.Rendered against live data — the page now shows the accurate current state (
.7backends up,.9backends down) instead of a confusing flicker.tsc+check:uiclean; agent/api tests updated for the gauge split.Note on the other two items
.9backends are stably down (9/9 samples), not flapping — so looseningcheckTimeout/maxCheckFailureswouldn't help. It's a hard cross-host failure, not jitter.proxy-protocol-fromalready lists both dists, so it's not that ACL. Need a real DNS/proxy-protocol probe tool on a .7 box or shell on .9.🤖 Generated with Claude Code