Cherry-pick #20325 to 7.9: system/socket: Allow running multiple instances by grouping kprobes by PID #20354
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cherry-pick of PR #20325 to 7.9 branch. Original message:
What does this PR do?
This updates the system/socket dataset to group installed kprobes by PID instead of using a generic
auditbeat
group.This allows multiple instances of Auditbeat to run with the system/socket dataset enabled (default) avoiding collision of kprobes.
Why is it important?
Currently is not possible to run more than one Auditbeat instance under Linux due to kprobes colliding.
Checklist
I've tested this in Ubuntu 18.04 / kernel 4.15 and it can run multiple instances without trouble.
[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files[ ] I have added tests that prove my fix is effective or that my feature worksCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related issues
Closes #20303