ns-ui / fusee-cone

Burn-rate alert policy

Drag the 4 control points to author how sensitive alerting gets as error budget depletes — the cone tapers toward the empty end because a control point can never be raised above the one before it. The table on the right is the rule set that shape implies; Replay streams a recorded burn history and stamps where it would have tripped.

CHECKOUT LATENCY SLOQUIET

burn 3.0x · 100% budget remaining · needs 14x here

Derived multi-window burn-rate alert rule table for Checkout latency SLO
Budget remainingWindowBurn multiplier
100%1h14x
75%3h7.7x
50%12h3.5x
25%1d1.7x
0%3d1.0x

Quiet: burn 3.0x is under the 14x threshold at 100% budget remaining.