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 60154d2
Browse filesBrowse the repository at this point in the historyBrowse files
fix(rpcsmartrouter): a provider out of the pairing passes none of the checks it was failing (MAG-3950)
A provider out of the pairing is listed by the check that took it out
alone, so everything else it failed left the list at the demote and
logged "verification check passes again", though nothing had checked
it. A provider with no ws url logged its missing url passing at each
demote, and failing again at each readmit (review of #602).
trackFailures now holds those failures while the provider is out: no
line at the demote, and at the readmit each goes on with its start, or
passes again then, counted from its start. The gauge publishes the
start the logs name, so a part failure that outlasts a demote comes back
with its own start, not the readmit's: the PartialFail alert of the
alert-by-severity branch posts at the readmit when that start is older
than 30 minutes. sr-verify-failed reads scope=provider alone and is
unchanged.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: docs/METRICS.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -655,7 +655,7 @@ self-heals in seconds. Alert windows should assume the 3m ceiling.
655
655
656
656
| Metric | Type | Labels | Description |
657
657
| --- | --- | --- | --- |
658
-
|`smartrouter_provider_verification_failed`| Gauge |`spec`, `apiInterface`, `provider`, `tier`, `scope`, `service`, `check`, `severity`| While a configured provider is failing a verification: the unix time in seconds the failure started. The series exists only while the failure lasts, and a provider that moves to another check in the same `scope` and `service` keeps its start (a `scope=none` warning never borrows another's). `tier` is `static` or `backup`. |
658
+
|`smartrouter_provider_verification_failed`| Gauge |`spec`, `apiInterface`, `provider`, `tier`, `scope`, `service`, `check`, `severity`| While a configured provider is failing a verification: the unix time in seconds the failure started. The series exists only while the failure lasts, and a provider that moves to another check in the same `scope` and `service` keeps its start (a `scope=none` warning never borrows another's). While a provider is out of the pairing it has only its `scope=provider` series; a failure it had before it went out comes back with its own start when it is readmitted and still fails, and no "passes again" line is logged for it at the demote. `tier` is `static` or `backup`. |
659
659
|`smartrouter_provider_verification_check_failures_total`| Counter | same as above | One per failed check run: at boot, each verification retry, and each 15m epoch pass (a grace run before a demotion included). A rate-limited run is inconclusive and not counted, on any path, and a missing websocket url (`missing-url`) ran nothing, so it is not counted either. `increase(...[$__interval]) > 0` draws one mark per failed run. |
660
660
661
661
The serving tier only drops when a whole tier is gone, so a single provider that fails
0 commit comments