429 Too Many Requests on Realtime connections with Project Alerts

Goal is to configure Supabase Project Alerts to signal real capacity issues without generating excessive notification noise, with particular attention to Realtime WebSocket behavior.

Project Alerts support thresholds for API usage, storage and database queries, but the dashboard does not expose fine-grained mute controls per metric. Evaluation is tied to a fixed 5-minute window without custom aggregation, and there is no documented auto-silence after manual acknowledgment. The alerting surface also lacks a REST API for programmatic suppression. The Realtime API documents a per-project connection limit and a 429 Too Many Requests response when the limit is exceeded, without clarifying whether the 429 is per-client or aggregated across all connections.

Is the 429 Too Many Requests response for Realtime emitted per client or aggregated across the project connection pool? Can a specific metric be muted or silenced within Project Alerts while keeping other metrics active? Is there a documented acknowledgment or suppression mechanism that prevents re-triggering on each evaluation window?