Cherry-pick #17360 to 7.x: Add regex based cid extractor to add_process_metadata#17462
Merged
exekias merged 2 commits intoelastic:7.xfrom May 8, 2020
Merged
Cherry-pick #17360 to 7.x: Add regex based cid extractor to add_process_metadata#17462exekias merged 2 commits intoelastic:7.xfrom
exekias merged 2 commits intoelastic:7.xfrom
Conversation
* Add regex based cid extractor to add_process_metadata Co-authored-by: Jako Tinkus <jatinkus@microsoft.com> (cherry picked from commit b92c6c3)
Contributor
|
Pinging @elastic/integrations-platforms (Team:Platforms) |
kaiyan-sheng
approved these changes
Apr 8, 2020
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
5 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 #17360 to 7.x branch. Original message:
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.asciidocorCHANGELOG-developer.next.asciidoc.Author's Checklist
How to test this PR locally
Related issues
Relates:
#15947
#17351
Use cases
Screenshots
Logs