Skip to content

Replication observability: time-at-full-buffer counter (alertable backpressure) #598

Description

@kriszyp

Fold-in from Chris Nelson's replication-monitoring wishlist (rider, 2026-07-15). Promoted out of the #532 coverage-map comment into a tracked sub-issue of #437 (W8).

Problem

The raw back-pressure percentage oscillates 0–100 on busy meshes, so the monitoring side has to smooth it downstream before it's usable — a smoothing step that hides exactly the sustained-full condition we want to alert on.

Ask

Add a monotonic time-at-full-buffer counter per link (seconds spent with the send buffer full). A counter is directly alertable (rate() > threshold) with no downstream smoothing, unlike the oscillating instantaneous %.

Acceptance criteria

  • Per-link cumulative time-at-full-buffer is queryable in cluster_status and scrapable per peer (harper#1636), and an alert can fire on sustained backpressure without client-side smoothing.

🤖 Filed by KrAIs on behalf of Kris.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Fields

    Priority

    P2

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions