Expand description
Outbound alerting (gateway L4) — threshold/regression alerts to Slack/webhook, in your own VPC.
When [alerts] is enabled, EdgeGuard fires a Slack-compatible alert ({ "text": … }) when a
hard-budget’s consumed ratio crosses a threshold — cost-regression alerting with no SaaS
alerting plane to depend on, and nothing leaving your own VPC.
Fire-and-forget: a background POST that never blocks or fails
the request. Edge-triggered: exactly one alert per crossing into the alert zone (tracked per
budget), so a busy proxy over-budget for a while doesn’t spam the channel.
First cut on budget breaches; the same shape extends to latency-percentile / error-rate / (via a
trace store) eval-drift rules — the rule decision (AlertRuntime::decide_budget) is pure and
the delivery is a generic webhook POST.
Structs§
- Alert
Runtime - Compiled alerting runtime, carried on the proxy
Runtime.