mirror of
https://github.com/netbirdio/netbird.git
synced 2026-09-12 17:59:06 +02:00
riccardom
e0523efe5a
The per-exchange lifecycle logs were all at LevelTrace (below the default field level) and did not distinguish a signalling re-bootstrap from a data-path rekey, which made diagnosing exchange activity in the field guesswork (e.g. telling an ICE-retry-driven re-bootstrap storm apart from normal KEM rotation). Promote the two pivotal events — an offer going out and a PSK converging — to LevelDebug and tag every lifecycle log with four dimensions: - msg: offer vs answer (implicit in the message) - role: initiator vs responder for this peer - via: signal vs data-path (threaded into processOffer/processAnswer) - kind: bootstrap (a new connection / reconnect) vs rotation (a rekey) kind is derived from the exchange's AckID (zero = bootstrap) on the responder side and from viaSignal on the initiator side. No behavioural change.