Cherry-pick #19221 to 7.8: [Metricbeat] Remove dedot for AWS tag value #19251
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 #19221 to 7.8 branch. Original message:
What does this PR do?
This PR is to remove dedotting when collecting AWS tag value. Only tag keys are dedotted, but keep tag values to be the original.
Why is it important?
For some use cases, tags value may contain dot, such as IPv4 address. There is no need to dedot when storing into ES in json event field value.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related issues
DeDot
is not unnecessary? #19112Screenshots
This is before and after comparison for tag value: