-
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
Add regex based cid extractor to add_process_metadata #17360
Conversation
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
1 similar comment
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
Here is optional regex based container id extractor functionality added to add_process_metadata. Regards, |
@exekias auto checks green and checklist check-boxes checked now :) |
Pinging @elastic/integrations-platforms (Team:Platforms) |
ok to test |
Thank you so much for contributing! Waiting for a green light from the CI |
* Add regex based cid extractor to add_process_metadata Co-authored-by: Jako Tinkus <jatinkus@microsoft.com> (cherry picked from commit b92c6c3)
What does this PR do?
Adds regex based cid extractor to add_kubernetes_metadata
Why is it important?
Adds more flexibility and makes possible to bypass bug with kube-proxy cid turning out to be "kube-proxy"
Checklist
- [ ] I have made corresponding change to the default configuration filesCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Author's Checklist
How to test this PR locally
Related issues
Relates:
#15947
#17351
Use cases
Screenshots
Logs