Conversation
8204ed0 to
9c9cac4
Compare
❕ Build Aborted
Expand to view the summary
Build stats
Test stats 🧪
Steps errors
Expand to view the steps failures
|
|
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
|
/test auditbeat integTest |
|
/test auditbeat integTest arm |
|
This pull request is now in conflicts. Could you fix it? 🙏 |
136b45c to
3e7db0b
Compare
|
/test auditbeat integTest arm |
|
/test auditbeat integTest arm |
There was a problem hiding this comment.
Just a few minor comments, I don't think anything that requires another look.
For future reference, in these larger changesets I would prefer if we didn't force push after the first peer review comments come in. Being able to view the changes since you last reviewed is valuable. At least in this repo, you are required to squash at merge so you still have an opportunity to clean up the commit message.
💚 Build Succeeded
History
cc @mmat11 |
💚 Build Succeeded
History
cc @mmat11 |
💚 Build Succeeded
History
cc @mmat11 |
💚 Build Succeeded
History
cc @mmat11 |
💚 Build Succeeded
History
cc @mmat11 |
💚 Build Succeeded
History
cc @mmat11 |
Proposed commit message
This PR adds an additional opt-in eBPF backend to the file_integrity module. See related issues for more context.
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Author's Checklist
How to test this PR locally
Enable the eBPF backend in the file_integrity module config by specifying
force_backend: ebpfand observe file events after running auditbeat.Related issues