-
Notifications
You must be signed in to change notification settings - Fork 211
Clarify Kibana xpack.alerting.rules.run.alerts.max setting #5783
Copy link
Copy link
Closed
elastic/kibana
#255608Labels
Docset: ESSIssues that apply to docs in the Stack releaseIssues that apply to docs in the Stack releaseDocset: ServerlessIssues for Serverless SecurityIssues for Serverless SecurityEffort: SmallIssues that can be resolved quicklyIssues that can be resolved quicklyFeature: RulesTeam: Detection Rule ManagementTeam: Detections/ResponseDetections and ResponseDetections and ResponseenhancementNew feature or requestNew feature or requestv8.12.0v8.13.0v8.14.0v8.15.0v8.16.0
Metadata
Metadata
Assignees
Labels
Docset: ESSIssues that apply to docs in the Stack releaseIssues that apply to docs in the Stack releaseDocset: ServerlessIssues for Serverless SecurityIssues for Serverless SecurityEffort: SmallIssues that can be resolved quicklyIssues that can be resolved quicklyFeature: RulesTeam: Detection Rule ManagementTeam: Detections/ResponseDetections and ResponseDetections and ResponseenhancementNew feature or requestNew feature or requestv8.12.0v8.13.0v8.14.0v8.15.0v8.16.0
Type
Fields
Give feedbackNo fields configured for issues without a type.
Description
What: we need to update a warning statement for xpack.alerting.rules.run.alerts.max setting on https://www.elastic.co/guide/en/kibana/current/alert-action-settings-kb.html page
Why: customers and elastic employees are confused whether the setting can be changed.
We should clarify that changing the setting to > 1000 is technically possible, but not recommended or supported. It should be carefully considered.
Related links / assets
Please include each of the following, if applicable:
Doc URL: https://www.elastic.co/guide/en/kibana/current/alert-action-settings-kb.html
Subject matter expert:
Figma link(s):
Github epic link(s):
Github issue link(s): elastic/kibana#173593
Which documentation set needs improvement?
ESS only
Software version
8.12 +
Collaborators
PM: @approksiu
Designer:
Developer: @dplumlee
Others (if applicable): @banderror
Timeline / deliverables
We have a couple of users now who were confused by this warning statement