-
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
[Alerting] Adding a configurable minimal rule interval for newly created rules #125396
Conversation
…g/minimum_rule_interval
Specifies whether to skip writing alerts and scheduling actions if rule execution is cancelled due to timeout. Default: `true`. This setting can be overridden by individual rule types. |
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.
I will make a separate PR to add this to the cloud allowlist.
@@ -139,7 +138,7 @@ export interface AlertingPluginsStart { | |||
} | |||
|
|||
export class AlertingPlugin { | |||
private readonly config: Promise<AlertsConfig>; | |||
private readonly config: AlertingConfig; |
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.
Not sure why this was a Promise, but I am able to get the config synchronously so I updated the code. If there's a reason it has to be a Promise, am happy to revert these changes.
…g/minimum_rule_interval
…g/minimum_rule_interval
@@ -161,6 +161,7 @@ export function createTestConfig(name: string, options: CreateTestConfigOptions) | |||
'--xpack.encryptedSavedObjects.encryptionKey="wuGNaIhoMpk5sO4UBxgr3NyW1sFcLgIf"', | |||
'--xpack.alerting.invalidateApiKeysTask.interval="15s"', | |||
'--xpack.alerting.healthCheck.interval="1s"', | |||
'--xpack.alerting.minimumScheduleInterval="1s"', |
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.
Setting minimum very short on functional tests.
Pinging @elastic/response-ops (Team:ResponseOps) |
Cloud allowlist PR: https://github.com/elastic/cloud/pull/98054 |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
Followup issue for enabling/disabling: #126409 |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
💚 Build SucceededMetrics [docs]Module Count
Public APIs missing comments
Async chunks
Page load bundle
Unknown metric groupsAPI count
History
To update your PR or re-run it, just comment with: cc @ymao1 |
…interval for rules Fixes failing cypress tests that are a result of this recent change within alerting - #125396 Rule min interval times now must be 1 minute or greater.
With this PR: #127498, we are changing the default behavior to warn instead of error so removing the breaking changes label. |
Resolves #124810
Summary
minimumScheduleInterval
from rule type registration since it was not used by any rule typeminimumScheduleInterval
tokibana.yml
configtriggers_actions_ui
pluginTo verify:
Breaking Change
We previously did not enforce any minimum schedule interval for rules. Adding this minimum may be a breaking change for users using automated methods to create or update their rules. If users are impacted by this change in behavior, they have the option of configuring
xpack.alerting.minimumScheduleInterval
to be a smaller value or increasing the interval of their alerting rules.Checklist