Files
rippled/docs
Pratik Mankawde d5f910cfca docs(telemetry): the tx-set fetch now has a span, so stop saying it has none
The consensus round-flow diagram marked `acquireTxSet -> gotTxSet` as having no
span, and styled it as a step with no instrumentation. That was true when the
diagram was written and stopped being true on this branch, which added the span.

The fetch is now `txset.acquire`, carrying one `round.request` event per round
that asked for the set. The `gotTxSet` delivery still has no span of its own, so
a set that arrives too late for the round to use it leaves no trace -- worth
stating, because that is the case an operator goes looking for.

Corrected on this branch rather than upstream on purpose: phase-9 and phase-10
carry the same diagram but not the span, so "no span" is accurate there. Moving
the fix upstream would describe instrumentation those branches do not have.
2026-08-26 17:02:58 +01:00
..
2020-03-30 18:57:35 -04:00