forked from elastic/kibana
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[8.x] [Rule Migration] Improve rule translation prompts and processes (…
…elastic#204021) (elastic#204109) # Backport This will backport the following commits from `main` to `8.x`: - [[Rule Migration] Improve rule translation prompts and processes (elastic#204021)](elastic#204021) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Marius Iversen","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-12T18:32:04Z","message":"[Rule Migration] Improve rule translation prompts and processes (elastic#204021)\n\n## Summary\n\nThis PR performs multiple changes that all focuses on improving the\nquality of the results returned when we translate rules that do not\nmatch with a prebuilt rule and both with/without related integrations.\n\nChanges include:\n\n- Add a filter_index_patterns node, to always ensure `logs-*` is removed\nwith our `[indexPattern:logs-*]` value, which is similar to how we\ndetect missing lookups and macros.\n- Split `translate_rule` into another `ecs_mapping` node, trying to\nensure translation focuses on changing SPL to ESQL without any focus on\nactual field names, while the other node focuses only on the ESQL query\nand changing field names.\n- The summary now added in the comments have 1 for the translation and\none for the ECS mapping.\n- Add default rule batch size `15` with PR comment/question.\n- Ensure we only return one integration related rather than an array for\nnow, to make ESQL more focused on one related integration.\n- New prompt to filter out one or more integrations from the returned\nRAG; similar to how its done for rules RAG results already.","sha":"0a7262d0fc213148fd7e80d3dc65f79c7eeae244","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team: SecuritySolution","backport:prev-minor","v8.18.0"],"title":"[Rule Migration] Improve rule translation prompts and processes","number":204021,"url":"https://github.com/elastic/kibana/pull/204021","mergeCommit":{"message":"[Rule Migration] Improve rule translation prompts and processes (elastic#204021)\n\n## Summary\n\nThis PR performs multiple changes that all focuses on improving the\nquality of the results returned when we translate rules that do not\nmatch with a prebuilt rule and both with/without related integrations.\n\nChanges include:\n\n- Add a filter_index_patterns node, to always ensure `logs-*` is removed\nwith our `[indexPattern:logs-*]` value, which is similar to how we\ndetect missing lookups and macros.\n- Split `translate_rule` into another `ecs_mapping` node, trying to\nensure translation focuses on changing SPL to ESQL without any focus on\nactual field names, while the other node focuses only on the ESQL query\nand changing field names.\n- The summary now added in the comments have 1 for the translation and\none for the ECS mapping.\n- Add default rule batch size `15` with PR comment/question.\n- Ensure we only return one integration related rather than an array for\nnow, to make ESQL more focused on one related integration.\n- New prompt to filter out one or more integrations from the returned\nRAG; similar to how its done for rules RAG results already.","sha":"0a7262d0fc213148fd7e80d3dc65f79c7eeae244"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/204021","number":204021,"mergeCommit":{"message":"[Rule Migration] Improve rule translation prompts and processes (elastic#204021)\n\n## Summary\n\nThis PR performs multiple changes that all focuses on improving the\nquality of the results returned when we translate rules that do not\nmatch with a prebuilt rule and both with/without related integrations.\n\nChanges include:\n\n- Add a filter_index_patterns node, to always ensure `logs-*` is removed\nwith our `[indexPattern:logs-*]` value, which is similar to how we\ndetect missing lookups and macros.\n- Split `translate_rule` into another `ecs_mapping` node, trying to\nensure translation focuses on changing SPL to ESQL without any focus on\nactual field names, while the other node focuses only on the ESQL query\nand changing field names.\n- The summary now added in the comments have 1 for the translation and\none for the ECS mapping.\n- Add default rule batch size `15` with PR comment/question.\n- Ensure we only return one integration related rather than an array for\nnow, to make ESQL more focused on one related integration.\n- New prompt to filter out one or more integrations from the returned\nRAG; similar to how its done for rules RAG results already.","sha":"0a7262d0fc213148fd7e80d3dc65f79c7eeae244"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Marius Iversen <[email protected]>
- Loading branch information
1 parent
ef852fc
commit b9fce2f
Showing
23 changed files
with
560 additions
and
89 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
Binary file modified
BIN
+10 KB
(130%)
x-pack/plugins/security_solution/docs/siem_migration/img/agent_graph.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.