Trying to create an SLO on serverless with a 30d (or 7d) backfill window can cause a lot of burden on the cluster, and make it unavailable for a while. Also, the SLO might not be successfully created due to timeout.
On serverless, we should not attempt to backfill data for more than a day. The option to prevent backfill can still be used, and will override the 1d limit.
Nothing should change on stateful.
Acceptance criteria
[ ] On stateful, the timestamp filter defaults to the slo time window
[ ] On stateful and serverless, the timestamp filter is 5m if "prevent backfill" is checked
[ ] On serverless, the timestamp filter defaults to 1d
kdelemme
commented
1 month ago
Summary
Related incident: https://elastic.slack.com/archives/C07BPA84NMA/p1721130693708489
Trying to create an SLO on serverless with a 30d (or 7d) backfill window can cause a lot of burden on the cluster, and make it unavailable for a while. Also, the SLO might not be successfully created due to timeout.
On serverless, we should not attempt to backfill data for more than a day. The option to prevent backfill can still be used, and will override the 1d limit.
Nothing should change on stateful.
Acceptance criteria