Provider health diagnostics 

Provider health and circuits 

A table lists every provider that is either configured and active or named by a run in the telemetry window, with its health score, the number of samples the score is based on, the window those samples were taken over, and the state of its circuit breaker.

Health and circuit state are both keyed by adapter type, not by provider record — two provider records on the same adapter share one score and one circuit, because it is the provider that is unhealthy, not the record.

Column Meaning
Score A single 0.00–1.00 number combining success rate and mean latency, success rate weighted four times as heavily (see ADR-063: Provider Resilience — Circuit Breaker, Health, Idempotency). Higher is healthier.
Samples in window How many runs the score was computed from. Read it before the score: 0.90 over two calls and 0.90 over two thousand are different statements.
Success rate Share of runs the provider served itself. A run a fallback rescued counts as a failure of the requested provider.
Avg latency Mean end-to-end time of the self-served runs. A provider whose runs in the window were all rescued by a fallback has no self-served run to measure: the cell says the latency was not measured instead of showing 0 ms. Its score and success rate are real — the first attempt did lose.
Circuit closed (normal), open (failing fast for the cooldown) or half-open (cooldown elapsed, one probe due), plus the current consecutive-failure streak.

Unlike the rest of this module the table ignores the date range selected above. Scores come from a rolling telemetry window (15 minutes by default, named on the page) and circuit state is live cache state — neither can be re-cut to a 90-day report period.

A provider with no telemetry in the window shows no data — not a score of zero. It was not called; that is not the same as failing.