You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit f685a7d
Browse filesBrowse the repository at this point in the historyBrowse files
docs(reference): PodID on /debug/sticky-claims, and what adopted does not prove (MAG-3860)
The route now names the process that answered, because the debug port is
reached through a Service that balances across replicas. And adopted also
counts a replica reading back its own claim after it dropped its local
copy, so the section says how to tell that from a peer's claim.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: docs/reference/metrics.md
+17-5Lines changed: 17 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -455,23 +455,35 @@ across every replica through a shared claim. Each resolution is counted by how i
455
455
456
456
| Metric | Type | Labels | Description |
457
457
| --- | --- | --- | --- |
458
-
|`smartrouter_csm_sticky_claims_total`| Counter |`spec`, `apiInterface`, `outcome`| Claim resolutions. `outcome`: `local_hit` (answered from this replica's confirmed claim), `adopted` (took a claim another replica had made), `claimed` (this replica made the claim), `lost_race` (a peer's claim naming a different upstream won), `error` (the claim could not be read or written, so the request failed), `no_candidate` (this replica had no upstream to offer), `invalidated` (a claim was dropped because its upstream could not serve here). |
458
+
|`smartrouter_csm_sticky_claims_total`| Counter |`spec`, `apiInterface`, `outcome`| Claim resolutions. `outcome`: `local_hit` (answered from this replica's confirmed claim), `adopted` (routed by a live claim read from the shared registry rather than one held in memory — usually a peer's, see below), `claimed` (this replica made the claim), `lost_race` (a peer's claim naming a different upstream won), `error` (the claim could not be read or written, so the request failed), `no_candidate` (this replica had no upstream to offer), `invalidated` (a claim was dropped because its upstream could not serve here). |
459
459
460
-
`adopted` is the outcome that proves a session crossed replicas. The `Lava-Provider-Address`
461
-
reply header reads the same whether a replica used its own claim or a peer's.
460
+
`adopted` is how a session that crossed replicas shows up. The `Lava-Provider-Address` reply
461
+
header reads the same whether a replica used its own claim or a peer's. `adopted` is not proof on
462
+
its own, though. A replica that drops its local copy of a claim (`invalidated`) leaves the shared
463
+
claim in place, so its next request reads its own claim back and counts `adopted` too. So does a
464
+
replica after `/debug/reset-all` clears its local table, if the shared claim outlived the reset. A
465
+
rise in `adopted` on a replica whose `invalidated` count did not move, with no reset in between, is
466
+
a peer's claim.
462
467
463
468
The same counts are readable without the metrics port at `GET /debug/sticky-claims` on the
464
469
debug server (`--debug-address`), one row per endpoint:
0 commit comments