Skip to content

[DOCS][8.18.3, 8.18.4, 8.19.0] [Known Issue] Rule issues occur when xpack.alerting.rules.run.alerts.max is set to a value greater than 5000#230835

Merged
nastasha-solomon merged 6 commits intoelastic:8.19from
nastasha-solomon:issue-230275-ki
Aug 6, 2025

Conversation

@nastasha-solomon
Copy link
Contributor

@nastasha-solomon nastasha-solomon commented Aug 6, 2025

Summary

Adds the known issue about the xpack.alerting.rules.run.alerts.max setting to the 8.18.3, 8.18.4, and 8.19.0 release notes. Related issue: #230275

Corresponding 9.x PR: #230837

Previews

@nastasha-solomon nastasha-solomon self-assigned this Aug 6, 2025
@nastasha-solomon nastasha-solomon added release_note:skip Skip the PR/issue when compiling release notes Team:ResponseOps Platform ResponseOps team (formerly the Cases and Alerting teams) t// backport:version Backport to applied version labels v8.19.0 v8.18.3 labels Aug 6, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Aug 6, 2025

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.

@nastasha-solomon nastasha-solomon changed the title [DOCS][8.18.3 & 8.19.0] [Known Issue] Rule issues occur when xpack.alerting.rules.run.alerts.max is set to a value greater than 5000 [DOCS][8.18.3, 8.18.4, 8.19.0] [Known Issue] Rule issues occur when xpack.alerting.rules.run.alerts.max is set to a value greater than 5000 Aug 6, 2025
@nastasha-solomon nastasha-solomon marked this pull request as ready for review August 6, 2025 16:31
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

cc @nastasha-solomon

Copy link
Contributor

@doakalexi doakalexi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@nastasha-solomon nastasha-solomon merged commit 59dfa8f into elastic:8.19 Aug 6, 2025
10 checks passed
nastasha-solomon added a commit that referenced this pull request Aug 6, 2025
…k.alerting.rules.run.alerts.max is set to a value greater than 5000 (#230837)

Adds the known issue about the `xpack.alerting.rules.run.alerts.max`
setting to the Kibana known issues page and marked it as a known issue
in 9.0.3, 9.0.4, and 9.1.0. Related issue:
#230275

**Corresponding 8.x PR**: #230835


[Preview](#230837 (comment))
gergoabraham pushed a commit to gergoabraham/kibana that referenced this pull request Aug 7, 2025
…k.alerting.rules.run.alerts.max is set to a value greater than 5000 (elastic#230837)

Adds the known issue about the `xpack.alerting.rules.run.alerts.max`
setting to the Kibana known issues page and marked it as a known issue
in 9.0.3, 9.0.4, and 9.1.0. Related issue:
elastic#230275

**Corresponding 8.x PR**: elastic#230835


[Preview](elastic#230837 (comment))
nastasha-solomon added a commit that referenced this pull request Aug 7, 2025
…rting.rules.run.alerts.max is set to a value greater than 5000 (#230872)

Manually ports changes from
#230835 to the 8.18 branch.
nastasha-solomon added a commit to nastasha-solomon/kibana that referenced this pull request Aug 7, 2025
…xpack.alerting.rules.run.alerts.max` is set to a value greater than 5000 (elastic#230835)

Adds the known issue about the `xpack.alerting.rules.run.alerts.max`
setting to the 8.18.3, 8.18.4, and 8.19.0 release notes. Related issue:
elastic#230275

**Corresponding 9.x PR**: elastic#230837

- [8.18.3 known
issues](https://kibana_bk_230835.docs-preview.app.elstc.co/guide/en/kibana/8.19/release-notes-8.18.3.html)
- [8.18.4 known
issues](https://kibana_bk_230835.docs-preview.app.elstc.co/guide/en/kibana/8.19/release-notes-8.18.4.html)
- [8.19.0 known
issues](https://kibana_bk_230835.docs-preview.app.elstc.co/guide/en/kibana/8.19/release-notes-8.19.0.html)
@mistic mistic added v8.19.2 and removed v8.19.0 labels Aug 7, 2025
nastasha-solomon added a commit to nastasha-solomon/kibana that referenced this pull request Aug 7, 2025
…k.alerting.rules.run.alerts.max is set to a value greater than 5000 (elastic#230837)

Adds the known issue about the `xpack.alerting.rules.run.alerts.max`
setting to the Kibana known issues page and marked it as a known issue
in 9.0.3, 9.0.4, and 9.1.0. Related issue:
elastic#230275

**Corresponding 8.x PR**: elastic#230835

[Preview](elastic#230837 (comment))
@nastasha-solomon nastasha-solomon deleted the issue-230275-ki branch August 7, 2025 22:02
denar50 pushed a commit to denar50/kibana that referenced this pull request Aug 8, 2025
…k.alerting.rules.run.alerts.max is set to a value greater than 5000 (elastic#230837)

Adds the known issue about the `xpack.alerting.rules.run.alerts.max`
setting to the Kibana known issues page and marked it as a known issue
in 9.0.3, 9.0.4, and 9.1.0. Related issue:
elastic#230275

**Corresponding 8.x PR**: elastic#230835


[Preview](elastic#230837 (comment))
NicholasPeretti pushed a commit to NicholasPeretti/kibana that referenced this pull request Aug 18, 2025
…k.alerting.rules.run.alerts.max is set to a value greater than 5000 (elastic#230837)

Adds the known issue about the `xpack.alerting.rules.run.alerts.max`
setting to the Kibana known issues page and marked it as a known issue
in 9.0.3, 9.0.4, and 9.1.0. Related issue:
elastic#230275

**Corresponding 8.x PR**: elastic#230835


[Preview](elastic#230837 (comment))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:version Backport to applied version labels release_note:skip Skip the PR/issue when compiling release notes Team:ResponseOps Platform ResponseOps team (formerly the Cases and Alerting teams) t// v8.18.3 v8.18.4 v8.19.2

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants