-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add max configuration for minimumScheduleInterval and number of actions #130465
Add max configuration for minimumScheduleInterval and number of actions #130465
Conversation
Pinging @elastic/response-ops (Team:ResponseOps) |
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: cc @mikecote |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
…ns (#130465) (#130552) * Add max configuration for minimumScheduleInterval and number of actions * Fix test execution -> run (cherry picked from commit d38333d) Co-authored-by: Mike Côté <[email protected]>
…ns (elastic#130465) * Add max configuration for minimumScheduleInterval and number of actions * Fix test execution -> run
PR relates to #129128 but should follow up with cloud allow-list fixes if any. To be followed up by @ersin-erdal.
In this PR, I'm adding the following limitations to the new 8.2 config settings:
xpack.alerting.rules.execution.actions.max
higher than100,000
xpack.alerting.rules.minimumScheduleInterval
to an interval greater than1d