Cherry-pick #19209 to 7.x: [Packetbeat] Add forwarded tag example to config for network tap #20309
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 #19209 to 7.x branch. Original message:
What does this PR do?
Add an example to packetbeat.yml of using the
forwarded
tag to disablehost
metadata fields when processing network data from network tap or mirror port.With the default config you simply add
tags: [forwarded]
and the processors will remove
host.*
(and not includeadd_host_metadata
).Why is it important?
For users collecting monitoring a network tap or mirror port its important to not include the
host
fields in events because this traffic did not originate on the Packetbeat host.Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related issues