Cherry-pick #15947 to 7.7: enrich container id from process id#17244
Merged
exekias merged 1 commit intoelastic:7.7from Mar 25, 2020
Merged
Cherry-pick #15947 to 7.7: enrich container id from process id#17244exekias merged 1 commit intoelastic:7.7from
exekias merged 1 commit intoelastic:7.7from
Conversation
* enrich container id from process id (cherry picked from commit 3cb957d)
leweafan
pushed a commit
to leweafan/beats
that referenced
this pull request
Apr 28, 2023
* enrich container id from process id (cherry picked from commit 3aaf027) Co-authored-by: Fang He <fangbrookhe@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 #15947 to 7.7 branch. Original message:
Type of change
What does this PR do?
This PR enables add process metadata to enrich container id in Kubernetes environment by cgroup using process id.
Why is it important?
Include important metadata of the container id in the Kubernetes environment, which beats don't have this ability yet.
Checklist
Author's Checklist
How to test this PR locally
Deploy Auditbeat in minikube with the include_cid set to true. Deploy an sshd server in minikube. After the Auditbeat is running, ssh into the sshd server, which will trigger an Auditbeat event. See if the event coming from the sshd container is enriched with container id
cidRelated issues
Closes #14967
Use cases
Screenshots
Logs