The Known keys list of Pong.gauges in pong.proto (lines 172-180) tells clients to expect:
SLA, clients, version, brothers, stalls, rtt, PPM.
But internal/server/heartbeat.go in APN-Network/node (lines 57-63) actually writes a different set:
SLA, clients, version, brothers, stalls, PPM, TUN.
So rtt is documented but never sent, and TUN is sent but never documented. The node README already had a sibling fix (node issue #72 dropped rtt from its prose), but the proto comment was missed, and TUN was added to the code without a matching line in the comment.
TUN carries h.jams.Value() — a per-minute count of slow TUN writes, in the same shape as PPM (see internal/server/server.go:44 and :282).
Suggested fix: in pong.proto, drop the "rtt" line and add a "TUN" line, e.g.
// "TUN" — slow TUN writes per minute on the Node-side
// of this client's tunnel (back-pressure signal,
// same shape as PPM).
The
Known keyslist ofPong.gaugesinpong.proto(lines 172-180) tells clients to expect:SLA,clients,version,brothers,stalls,rtt,PPM.But
internal/server/heartbeat.goin APN-Network/node (lines 57-63) actually writes a different set:SLA,clients,version,brothers,stalls,PPM,TUN.So
rttis documented but never sent, andTUNis sent but never documented. The node README already had a sibling fix (node issue #72 droppedrttfrom its prose), but the proto comment was missed, andTUNwas added to the code without a matching line in the comment.TUNcarriesh.jams.Value()— a per-minute count of slow TUN writes, in the same shape asPPM(seeinternal/server/server.go:44and:282).Suggested fix: in
pong.proto, drop the"rtt"line and add a"TUN"line, e.g.