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
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Fixed
Chat health no longer cries wolf over one old failure. The sensor used to
read degraded if the add-on's rolling window held any failed chat, and that
window is trimmed by count (the last 50 chats), never by age — so on a quiet
install a single blip could keep the sensor red for days. It now reads degraded on three failed chats in a row, or when one chat in ten or more is
failing; and clears again once the clean chats since the last failure outnumber
the failures behind them, or that failure is over 6 hours old. One failure 19 hours ago with 37 clean chats since now reads ok, with the
detail still in the attributes — while a fault that keeps recurring stays
visible instead of being averaged away.
Added
A live outage shows up immediately. Three failed chats in a row now reads degraded on its own, without waiting for the failure rate to climb. A rate
measured over the last 50 chats can't see a fresh outage until it has diluted
that window — on a quiet install, potentially days.
Chat health shows its working. New attributes: recent_ok, failure_rate,
and — from add-on 1.49.0 — consecutive_ok / consecutive_failed (chats since
the last failure, and since the last success) plus last_failure, window_from and window_to, so you can see when the trouble was, not just
that there was some. On an older add-on those are null and the sensor judges on
the rate alone; a missing field neither clears a warning nor invents one.