diff options
| author | tv <tv@krebsco.de> | 2026-11-02 16:42:25 +0100 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-02 16:42:25 +0100 |
| commit | 810bf840d6318ecfab0709989067421925f12504 (patch) | |
| tree | 6a884c74065f9e876ff4a87fc7c88eee71d3bb6b /docs | |
| parent | b922d055a2208f5610c704a04309b14e1cbceb05 (diff) | |
add per-node traffic counts
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/measurements.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/measurements.md b/docs/measurements.md index 2adc0f5..fb01de0 100644 --- a/docs/measurements.md +++ b/docs/measurements.md @@ -168,9 +168,9 @@ 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, counted under the address they went to or came from, so only in the totals, and -`paths` for PING and PONG: per peer, but the paths layer's own PINGs under the address, -so only in the totals). Payload bytes are what a transport's message carries (the wire +ME, and `paths` for PING and PONG). 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 +(`/peers`) has those of its addresses too, where it is known to be at them. Payload bytes are what a transport's message carries (the wire encoding): not the transport's framing (for Mycelium, its topic and the base64 of its HTTP API). `refused` is what the transports wouldn't accept to send (no path to the peer), not counted as sent. |
