aboutsummaryrefslogtreecommitdiffstats
path: root/docs/measurements.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-07 22:35:10 +0100
committertv <tv@krebsco.de>2026-11-07 22:35:10 +0100
commit0e03a77bcb1d39f1fbda23d8e704ac40302afb93 (patch)
tree79245416e9721cdccb1b6879b8f1cfc43629cc74 /docs/measurements.md
parentc016fc783ff29e9069a446e17876046df64760a8 (diff)
dashboard: without LINKS; LINKS removed
The dashboard reads every member's links from the members themselves; LINKS and LINKS_REPLY, swarm::links and their wire tags go (wire version bumped). Nodes the browser can't reach are drawn from what the reachable ones measure. Auth plan M3.
Diffstat (limited to 'docs/measurements.md')
-rw-r--r--docs/measurements.md13
1 files changed, 6 insertions, 7 deletions
diff --git a/docs/measurements.md b/docs/measurements.md
index a444862..9036031 100644
--- a/docs/measurements.md
+++ b/docs/measurements.md
@@ -2,8 +2,7 @@
What a node measures about itself and its peers, where to read it, and what the
numbers mean. Everything here comes from traffic and work the node has anyway; it
-sends no probes of its own and nothing is measured by anyone else, but for the
-dashboard's map (LINKS, only while someone looks at it).
+sends no probes of its own and nothing is measured by anyone else.
Four places to read:
@@ -179,7 +178,7 @@ clocks"); setting them is the operating system's job (NTP).
Messages and payload bytes by direction (`sent`, `received`, `refused`) and kind
(`hello`, `helloReply`, `sync`, `status`, `statusReply`, `blob`, `identity` for WHO and
-ME, `paths` for PING and PONG, `links` for LINKS and their replies, `probe` for PROBE
+ME, `paths` for PING and PONG, `probe` for PROBE
and PROBE_REPLY, `plumtree` for PRUNE and GRAFT, `hyparview` for NEIGHBOUR,
NEIGHBOUR_REPLY and DISCONNECT). The layers below the node count WHO and ME, and the
paths layer's own PINGs and PONGs, under the address they went to or came from; a peer
@@ -302,13 +301,13 @@ outgrowing the full save (busy swarm, or a `--document-rewrite` set low).
In builds with the `dashboard` cargo feature, `GET /admin/dashboard` is a page showing
`/admin/stats`, `/peers` and a map of the swarm, live: [`dashboard.md`](dashboard.md), and how it works
-underneath (events, LINKS) at its end. Its LINKS are the one thing a node sends only to
-measure: the links every member reports, while someone looks.
+underneath (events, subscriptions) at its end. Other members' links it reads from
+them, over HTTP, from the nodes the page subscribes to: no messages in the swarm.
## What is not measured
-* Nothing about other nodes but what they send us: no probes, no remote figures (but
- the dashboard's LINKS).
+* Nothing about other nodes but what they send us: no probes, no remote figures (the
+ dashboard's page reads those of the nodes it subscribes to from them).
* Clock skew between nodes that aren't each other's peers: only peers' clocks are
compared (`clock`, per peer).
* Remake durations and outcomes: the remake reports (`GET /admin/remakes`) hold them.