-
Notifications
You must be signed in to change notification settings - Fork 474
[Enhancement] Modsecurity event coverage #4521
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
Conversation
/test |
🚀 Benchmarks reportPackage
|
Data stream | Previous EPS | New EPS | Diff (%) | Result |
---|---|---|---|---|
auditlog |
1223.99 | 897.67 | -326.32 (-26.66%) | 💔 |
To see the full report comment with /test benchmark fullreport
🌐 Coverage report
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm wondering whether it would be valuable to have modsecurity.request.headers
and modsecurity.response.headers
both as flattened. This could be guarded by an advanced option to prevent overloading indices.
Co-authored-by: Dan Kortschak <90160302+efd6@users.noreply.github.com>
@efd6 I have no actual opinion on this xD |
/test |
It is always something that we can add in the future if it becomes needed. |
/test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
What does this PR do?
This PR is aimed at getting better coverage on Modsecurity logs.
Mostly focused on the http request side (response is already covered well)
also some bugfix with missing fields ;)
Checklist
changelog.yml
file.