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

Fix Correlation rules finalization #278

Merged
merged 3 commits into from
Sep 17, 2024
Merged

Conversation

m4dh4t
Copy link
Contributor

@m4dh4t m4dh4t commented Sep 17, 2024

Fix #277

@m4dh4t m4dh4t changed the base branch from issue-277 to main September 17, 2024 12:15
@m4dh4t
Copy link
Contributor Author

m4dh4t commented Sep 17, 2024

@thomaspatzke this seems to do the job when running the tests locally, what do you think ?

@thomaspatzke
Copy link
Member

thomaspatzke commented Sep 17, 2024

Awesome! 👍 Functionally, it fixes the issue, just some black reformatting is required, just doing this and then merging.

Thanks!

@thomaspatzke thomaspatzke marked this pull request as ready for review September 17, 2024 21:54
@thomaspatzke thomaspatzke merged commit ba25155 into SigmaHQ:main Sep 17, 2024
15 checks passed
@m4dh4t m4dh4t deleted the issue-277 branch September 18, 2024 05:47
@m4dh4t
Copy link
Contributor Author

m4dh4t commented Sep 18, 2024

Looks like this change is breaking for the Elasticsearch ES|QL backend due to the way it handles correlation (Splunk looks good though). I have a fix ready and will open a dedicated issue on the repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Query postprocessing with correlation rules uses only search part of generated query
2 participants