serversdown/series3-watcher
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 7 Wiki Activity

7 Releases 7 Tags

RSS Feed
  • v1.6.0 fb1edfbad4
    Compare

    v1.6.0 - Optional dual-send mirror for standby/backup server Stable

    serversdown released this 2026-06-25 11:55:15 -04:00 | 2 commits to main since this release

    Added — Mirror (dual-send)

    • Post every heartbeat and event to a second ("mirror") server in addition to the primary. When MIRROR_API_URL and/or MIRROR_SFM_URL are set, each heartbeat POST and each forwarded Blastware event is also sent to the mirror destination — letting a standby box (e.g. the office NAS) stay a continuous replica of prod during a migration so the eventual cutover is a non-event. Default off — blank URLs mean existing 1.5.x installs don't change behaviour after an auto-update.
    • Heartbeat mirror (best-effort). After the primary send_api_payload, the same payload is fired at MIRROR_API_URL when set. It is fully wrapped and bounded by the existing API timeout — the mirror can never delay or fail the primary heartbeat; its outcome is ignored except for a debug log line.
    • Event mirror (reliable, isolated). Events are re-forwarded to MIRROR_SFM_URL through a separate sha256 state file (MIRROR_SFM_STATE_FILE, blank → <log dir>/sfm_forwarded_mirror.json) so the mirror tracks its own delivery independently of the primary forwarder. Before each mirror pass a quick reachability probe (~3 s) checks the mirror server; if it's down the pass is skipped and retried next tick rather than blocking the loop on per-event timeouts. Skipped events stay pending in the mirror state and deliver once the mirror returns — no data loss.
    • Isolation invariant. Nothing on the mirror path can delay or fail the primary: its own state file, its own try/except, the reachability guard + bounded timeouts, and all exceptions swallowed-and-logged. The primary path stays exactly as reliable as before. The mirror rides along with the primary — there is no separate enable flag (heartbeat-mirror active iff the primary heartbeat is on and MIRROR_API_URL is set; event-mirror active iff primary forwarding is on and MIRROR_SFM_URL is set).
    • Mirror fields in the Settings dialog: Mirror API URL + Mirror SFM URL (blank = off).
    • New unit tests in test_event_forwarder.py covering mirror reachability, the down-mirror skip, separate-state idempotency, and the isolation invariant (a mirror failure leaves the primary's result + state untouched).

    Configuration

    New [agent] keys (all default-off — existing 1.5.x deployments don't change behaviour on auto-update):

    Key Default Notes
    MIRROR_API_URL empty Second heartbeat base URL, e.g. http://10.0.0.x:8001 (blank = off)
    MIRROR_SFM_URL empty Second SFM base URL, e.g. http://10.0.0.x:8200 (blank = off)
    MIRROR_SFM_STATE_FILE <log dir>/sfm_forwarded_mirror.json Override location of the mirror's forwarded-sha256 state file

    Operational (migration seeding)

    To make the mirror re-deliver only the gap since a one-time replica snapshot, copy the primary state file to the mirror state file and drop entries whose forwarded_at is after the snapshot. SFM-side dedup covers any overlap. See docs/mirror-dual-send-design.md.

    Downloads