Try a rule against a historical stretch
POST/alarm-rules/backtest
Replays a rule over a historical period and returns the alarms that would have come into existence, including the effect of the debouncing. The rule does not have to be stored. Deliberately an aid for choosing thresholds and delays and NOT a historical record - the evaluation uses the properties that are valid today, so it is not suitable as evidence towards third parties. Responds 400 when the rule cannot be evaluated, the period cannot be resolved, or the backtest would cost more than allowed - computation (ticks of the schedule times bound objects, weighted with the data points per window) or data points to read. That last refusal carries backtestLimit with the longest period within the bound (HET-2222).
Request
Responses
- 200
- 400
- 401
- 403
- default
OK
The rule cannot be evaluated, the period cannot be resolved, or the backtest exceeds its budget - then backtestLimit names the bound and the longest period within it.
Unauthorized — the bearer token is missing, expired or invalid, or carries no role. Errors raised by the security aspects contain an ErrorDto body; requests rejected by the security filter chain may have an empty body.
Forbidden — the authenticated user lacks the required role or access rights.
the default error response