-
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
[DOC] Add notes to Packetbeat docs related to bonded interfaces #21752
Comments
botelastic
bot
added
the
needs_team
Indicates that the issue/PR needs a Team:* label
label
Oct 13, 2020
joshjanoski
added
Team:Docs
Label for the Observability docs team
and removed
needs_team
Indicates that the issue/PR needs a Team:* label
labels
Oct 13, 2020
Pinging @elastic/obs-docs (Team:Docs) |
andresrc
added
Team:Security-External Integrations
Team:Docs
Label for the Observability docs team
and removed
Team:Docs
Label for the Observability docs team
Team:Security-External Integrations
labels
Oct 15, 2020
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is in relation to the issue here: #21495 that is currently being looked into. If this issue is resolved, then a doc enhancement may not be needed, but I wanted to call out a specific scenario that would be worth noting until this is resolved.
The page here: https://www.elastic.co/guide/en/beats/packetbeat/current/configuration-interfaces.html#_sniffing_configuration_options shows an example of configuring the
packetbeat.interfaces.device: any
parameter. However, when setting theany
value for this parameter while using a bonded network interface, you will encounter an issue where Packetbeat will attempt to send null values for some fields (notably thedns.resolved_ip
andrelated.ip
fields). As a result, some log lines will fail to index due to these conflicts.The current workaround is to change the
packetbeat.interfaces.device:
parameter fromany
to the specific name of the bonded interface. Can the documentation please be updated to include a note related to bonded interfaces letting readers know that they may need to account for this issue in their config if using bonded interfaces. Thank you!The text was updated successfully, but these errors were encountered: