Skip to content
Open
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions docs/api/directives.md
Original file line number Diff line number Diff line change
Expand Up @@ -173,8 +173,9 @@ Smart Router annotates every response with metadata about how the relay was serv

| Header | Meaning |
|---|---|
| `Lava-Provider-Address` | The node that ultimately served the response. |
| `Lava-Retries` | Number of retry attempts made for this relay. |
| `Lava-Provider-Address` | The node that served the response. When the request took more than one attempt, every node the router tried, comma-separated in the order it asked them, with the node that served the response last (`Cached` when the answer came from the cache). |
| `Lava-Retries` | Attempts beyond the first that the router sent for this request, including a [hedged](../configuration/failover/hedge.md) attempt it cancelled because another node answered first. Absent when the request took one attempt. A write's fan-out to every node is one attempt and never reports retries. |
| `lava-hedge-triggered` | `true` when the router sent a parallel [hedged](../configuration/failover/hedge.md) attempt for this request. Absent otherwise; never `false`. |
| `Provider-Latest-Block` | Latest block the serving node reported. |
| `Lava-Guid` | Unique request id — correlate with logs and traces. |
| `Lava-Errored-Providers` | Nodes that errored on this request. |
Expand Down
2 changes: 2 additions & 0 deletions docs/configuration/failover/hedge.md
Original file line number Diff line number Diff line change
Expand Up @@ -55,4 +55,6 @@ The hedge tick interval is currently chain-derived (from `average_block_time` an
| `smartrouter_hedge_attempts` | histogram of hedge relays per request (buckets 1…10) |
| Tracing | each hedged attempt is a parallel span under the same parent |

On the response, a hedge sets `lava-hedge-triggered: true`, and the attempt that lost the race still counts in `Lava-Retries` and is named in `Lava-Provider-Address`, even though the router cancelled it once the winner answered. See [Response headers](../../api/directives.md#response-headers).

See the [Metrics reference](../../reference/metrics.md#hedging) for labels and types.