3x-ui/docs/public
Grigoriy 2f62dadd25
feat(notifications): add a failed-check threshold for node.down alerts (#6768)
One lost heartbeat on a lossy link flipped a node offline and sent node.down,
and the next probe sent node.up, so a flaky node flooded Telegram, email and
Discord with alert pairs.

A new nodeDownThreshold setting (default 1, today's behaviour) works like
outboundDownThreshold: node.down fires once the failed-check streak reaches it,
once per outage, and node.up only after a node.down was sent. The announcement
is persisted in nodes.down_notified, so a restart inside the threshold window
neither drops the outage's node.down nor re-announces nodes already reported
offline; nodes offline at upgrade are seeded as announced.
2026-10-24 04:26:13 +02:00
..
CNAME docs: vendor the documentation site into the monorepo 2026-07-07 23:07:14 +02:00
favicon.png docs: vendor the documentation site into the monorepo 2026-07-07 23:07:14 +02:00
icon.png docs: vendor the documentation site into the monorepo 2026-07-07 23:07:14 +02:00
logo-dark.png docs: vendor the documentation site into the monorepo 2026-07-07 23:07:14 +02:00
logo-light.png docs: vendor the documentation site into the monorepo 2026-07-07 23:07:14 +02:00
openapi.json feat(notifications): add a failed-check threshold for node.down alerts (#6768) 2026-10-24 04:26:13 +02:00