Indicators
Backtest before activating
"With this threshold, how many alerts would have fired?" — the question that earns a number the right to be believed.
Last updated 1 min readFor workspace admins
The only way to choose a number
Most thresholds are guessed, and then either alert so often nobody looks at them, or stay so quiet nobody remembers they exist.
A backtest fixes that: it tells you exactly how many times this threshold would have fired over past periods. A laxer band always fires strictly fewer times, which is what makes the comparison meaningful.
A backtest leaves no trace
Nothing is stored, no alert is sent, and no task lands on the board.
It is deterministic too: the same inputs always give the same number, so you can line several thresholds up and compare them.
Read this next
Still stuck?
If the answer wasn't here, write to us. It is a real inbox and it gets answered.