-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[Auditbeat] fim(kprobes): enrich file events by coupling add_process_metadata processor #38716
Conversation
50d3e2a
to
805857d
Compare
Pinging @elastic/sec-linux-platform (Team:Security-Linux Platform) |
Pinging @elastic/elastic-agent (Team:Elastic-Agent) |
3175213
to
56fa5d7
Compare
This pull request is now in conflicts. Could you fix it? 🙏
|
💔 Tests Failed
Expand to view the summary
Build stats
Test stats 🧪
Test errorsExpand to view the tests failures> Show only the first 10 test failures
|
56fa5d7
to
7364d3a
Compare
…eys do not contain dots
7364d3a
to
2a97039
Compare
805857d
to
026f848
Compare
026f848
to
aa7702e
Compare
aa7702e
to
392e265
Compare
bc709dd
to
6b0bae8
Compare
Proposed commit message
This PR adds reporting of process.group.id, process.group.name and process.entity_id in
add_process_metadata
processor. Also it changes the factory of MetricSets to allow the latter to specify Processors after successful instantiation; this is required as FIM has 3 different available backends, namelyfsnotify
,kprobes
,ebpf
and only thekprobes
one requires to haveadd_process_metadata
processor. Utilising the former,kprobes
backend always adds a properly configuredadd_process_metadata
processor. As a result, enriching kprobes file events with process-related data exhibits the same robustness levels of the currentadd_process_metadata
processor. However, the current design is aligned with @nick-alayil and thesec-linux-platform
which plan to increase the robustness ofadd_process_metadata
processor in a separate effort.Checklist
I have made corresponding change to the default configuration filesI have added tests that prove my fix is effective or that my feature worksCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Author's Checklist
How to test this PR locally
Related issues
Screenshots