-
Notifications
You must be signed in to change notification settings - Fork 518
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
[FR] [Implementation] Smart Limits for Detection Rules #4388
Comments
Pseudo Code and Preliminary Testing
|
what if there is only one version? |
Update 24 Jan Pseudo Code and Preliminary Testing
@Mikaayenson This ensure no rules with one version is removed. Also this opens up a possibility of another angle, where we could pick
The trimming would some like this.
cc @eric-forte-elastic / @traut for thoughts |
@Mikaayenson Not necessarily right. Assuming we have forked at version 1 so we get the version 100 and then there are updates for rule fork and older supported version. 6 would be latest than 100 :) Well i did crack my head in the afternoon for the same. if we had forked at version 6 then fork version would be 106 making it latest than base version 6 |
Repository Feature
Core Repo - (rule management, validation, testing, lib, cicd, etc.)
Problem Description
Per discussion(s) in - #4150, the previous limit for rule assets was removed to introduce historical package versions in 8.17.1 and 8.17.2. With this change the current asset count in rule package is close ~11500 and the tested asset limit on serverless projects is ~15000 before we hit OOM issues on serverless instances.
We need to reintroduce "smart limits" on detection rules to ensure there is minimum disruption to rule version diff feature in product that is used to analyse rule upgrades.
Desired Solution
With some brainstorming ides on the SWG call, there are 2 possible solutions to this issue.
Solution 1
Solution 2
For both of these solutions we need to revist code at keep_latest_versions
Considered Alternatives
Be able to handle rule asset management from the product side, this is being considered as a solution to ensure there is enough time for product enhancements
Additional Context
#4150
The text was updated successfully, but these errors were encountered: