github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-24 09:48:58 -04:00
Code Issues Projects Releases Packages Wiki Activity

[8.11] [DOCS] Add maxScheduledPerMinute to alerting circuit breakers (#169991) (#170145)

Browse source 
# Backport

This will backport the following commits from `main` to `8.11`:
- [[DOCS] Add maxScheduledPerMinute to alerting circuit breakers
(#169991)](https://github.com/elastic/kibana/pull/169991)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Lisa
Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2023-10-30T15:41:54Z","message":"[DOCS]
Add maxScheduledPerMinute to alerting circuit breakers
(#169991)","sha":"bbd4800ac435e0a24b243984986bb92692429b5f","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Alerting","release_note:skip","Team:ResponseOps","docs","backport:prev-minor","v8.11.0","v8.12.0"],"number":169991,"url":"https://github.com/elastic/kibana/pull/169991","mergeCommit":{"message":"[DOCS]
Add maxScheduledPerMinute to alerting circuit breakers
(#169991)","sha":"bbd4800ac435e0a24b243984986bb92692429b5f"}},"sourceBranch":"main","suggestedTargetBranches":["8.11"],"targetPullRequestStates":[{"branch":"8.11","label":"v8.11.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/169991","number":169991,"mergeCommit":{"message":"[DOCS]
Add maxScheduledPerMinute to alerting circuit breakers
(#169991)","sha":"bbd4800ac435e0a24b243984986bb92692429b5f"}}]}]
BACKPORT-->

Co-authored-by: Lisa Cawley <lcawley@elastic.co>
This commit is contained in:
Kibana Machine 2023-10-30 12:07:13 -04:00 • committed by GitHub
parent f84f590620
commit 1aa324325a
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

7
docs/user/production-considerations/alerting-production-considerations.asciidoc
View file

@ -72,6 +72,11 @@ There are several scenarios where running alerting rules and actions can start t
Running large numbers of rules at very short intervals can quickly clog up Task Manager throughput, leading to higher schedule drift. Use `xpack.alerting.rules.minimumScheduleInterval.value` to set a minimum schedule interval for rules. The default (and recommended) value for this configuration is `1m`. Use `xpack.alerting.rules.minimumScheduleInterval.enforce` to specify whether to strictly enforce this minimum. While the default value for this setting is `false` to maintain backwards compatibility with existing rules, set this to `true` to prevent new and updated rules from running at an interval below the minimum.
Another related setting is `xpack.alerting.rules.maxScheduledPerMinute`, which limits the number of rules that can run per minute.
For example if it's set to `400`, you can have 400 rules with one minute check intervals or 2,000 rules with 5 minute check intervals.
You cannot create or edit a rule if its check interval would cause this setting to be exceeded.
To stay within this limit, delete or disable some rules or update the check intervals so that your rules run less frequently.
[float]
==== Rules that run for a long time
@ -106,4 +111,4 @@ xpack.alerting.rules.run:
connectorTypeOverrides:
- id: '.email'
max: 200
--
--