Cherry-pick #22150 to 7.10: Move cloudfoundry tags with metadata to common metadata fields#22212
Merged
jsoriano merged 1 commit intoelastic:7.10from Oct 28, 2020
Merged
Conversation
Contributor
|
Pinging @elastic/integrations-platforms (Team:Platforms) |
Contributor
Member
Author
|
jenkins run the tests please |
1 similar comment
Member
Author
|
jenkins run the tests please |
sayden
approved these changes
Oct 28, 2020
Contributor
sayden
left a comment
There was a problem hiding this comment.
I think that changelog entry must be added according to comment #22150 (comment)
exekias
approved these changes
Oct 28, 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
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 #22150 to 7.10 branch. Original message:
What does this PR do?
In some Cloud Foundry deployments, metadata is included in tags, move these tags to the common fields.
Why is it important?
Adding metadata with
add_cloudfoundry_metadataimplies querying the app metadata APIs, and storing the returned values in a local cache. This may be not needed in deployments that already include metadata the events from the firehose.Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc. (Move cloudfoundry tags with metadata to common metadata fields #22150 (comment))Related issues