Skip to content
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

[Security Solution][Detection Engine] Investigate ways to bound memory usage of rule queries #192732

Open
marshallmain opened this issue Sep 12, 2024 · 1 comment
Labels
Feature:Detection Rules Anything related to Security Solution's Detection Rules performance Team:Detection Engine Security Solution Detection Engine Area

Comments

@marshallmain
Copy link
Contributor

Parent issue: https://github.com/elastic/security-team/issues/10106

Detection rules typically fetch 100 source documents at a time to transform into alerts. When these source documents are large, this puts significant memory pressure on both Elasticsearch and Kibana. If the documents are large enough, Elasticsearch and/or Kibana can run out of memory and crash. We should investigate ways that we can limit the total amount of data retrieved at one time to avoid OOM problems.

@marshallmain marshallmain added Feature:Detection Rules Anything related to Security Solution's Detection Rules performance Team:Detection Engine Security Solution Detection Engine Area labels Sep 12, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detection-engine (Team:Detection Engine)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Detection Rules Anything related to Security Solution's Detection Rules performance Team:Detection Engine Security Solution Detection Engine Area
Projects
None yet
Development

No branches or pull requests

2 participants