[Entity Store] Change defaults to conservative values#270617
Merged
Conversation
uri-weisman
approved these changes
May 22, 2026
romulets
added
backport:version
elastic-vault-github-plugin-prod
Bot
requested a review
from a team
as a code owner
Contributor
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]
History
cc @romulets |
Contributor
|
Starting backport for target branches: 9.4 https://github.com/elastic/kibana/actions/runs/26297016087 |
Contributor
💔 All backports failed
Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
This was referenced May 24, 2026
Member
Author
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
romulets
added a commit
that referenced
this pull request
May 25, 2026
…#270915) # Backport This will backport the following commits from `main` to `9.4`: - [[Entity Store] Change defaults to conservative values (#270617)](#270617) <!--- Backport version: 11.0.2 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Rômulo Farias","email":"romulo.farias@elastic.co"},"sourceCommit":{"committedDate":"2026-05-22T15:34:53Z","message":"[Entity Store] Change defaults to conservative values (#270617)\n\n## Summary\n\nUpdate entity store defaults to a conservative number:\n- maxLogsPerPage: 50k \n- maxLogsPerWindow: 100k\n\nMeaning, we will process at most 50k logs in each query of entity store,\nand in a single window, if it observes more than 100k logs (two pages)\nwe don't process those logs.\n\nThis can be configured via update api to better align with customers'\nsetup and needs.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"b9560c557118b03d3fa340140df992abc81307e8","branchLabelMapping":{"^v9.5.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:version","v9.4.0","v9.5.0"],"title":"[Entity Store] Change defaults to conservative values","number":270617,"url":"https://github.com/elastic/kibana/pull/270617","mergeCommit":{"message":"[Entity Store] Change defaults to conservative values (#270617)\n\n## Summary\n\nUpdate entity store defaults to a conservative number:\n- maxLogsPerPage: 50k \n- maxLogsPerWindow: 100k\n\nMeaning, we will process at most 50k logs in each query of entity store,\nand in a single window, if it observes more than 100k logs (two pages)\nwe don't process those logs.\n\nThis can be configured via update api to better align with customers'\nsetup and needs.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"b9560c557118b03d3fa340140df992abc81307e8"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"9.4","label":"v9.4.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/270892","number":270892,"state":"OPEN"},{"branch":"main","label":"v9.5.0","branchLabelMappingKey":"^v9.5.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/270617","number":270617,"mergeCommit":{"message":"[Entity Store] Change defaults to conservative values (#270617)\n\n## Summary\n\nUpdate entity store defaults to a conservative number:\n- maxLogsPerPage: 50k \n- maxLogsPerWindow: 100k\n\nMeaning, we will process at most 50k logs in each query of entity store,\nand in a single window, if it observes more than 100k logs (two pages)\nwe don't process those logs.\n\nThis can be configured via update api to better align with customers'\nsetup and needs.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"b9560c557118b03d3fa340140df992abc81307e8"}}]}] BACKPORT-->
jcger
pushed a commit
that referenced
this pull request
May 26, 2026
## Summary Update entity store defaults to a conservative number: - maxLogsPerPage: 50k - maxLogsPerWindow: 100k Meaning, we will process at most 50k logs in each query of entity store, and in a single window, if it observes more than 100k logs (two pages) we don't process those logs. This can be configured via update api to better align with customers' setup and needs. --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Update entity store defaults to a conservative number:
Meaning, we will process at most 50k logs in each query of entity store, and in a single window, if it observes more than 100k logs (two pages) we don't process those logs.
This can be configured via update api to better align with customers' setup and needs.