-
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
Cherry-pick #19767 to 7.x: add_process_metadata processor adds container id even if process metadata not accessible #20417
Conversation
…data not accessible (elastic#19767) (cherry picked from commit 99191e9)
Pinging @elastic/integrations-platforms (Team:Platforms) |
💔 Build FailedExpand to view the summary
Build stats
Test stats 🧪
Steps errorsExpand to view the steps failures
Log outputExpand to view the last 100 lines of log output
|
Cherry-pick of PR #19767 to 7.x branch. Original message:
What does this PR do?
Changed add_process_metadata processor to get both process metadata and container id and not error out if only one is available.
Why is it important?
If container is non-privileged, then process metadata for external processes is not fully readable (no access to /proc/pid/exe and /proc/pid/cwd) and code errors out before even trying to get container id. Same time container id is still accessible in /proc/pid/cgroup file. Now process metadata is skipped for such processes, but container id is still added.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Minor fix, probably no need for doc or changelog.
Author's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs