Cherry-pick #10029 to 6.6: Handle IPv6 zone id in IIS filebeat ingest pipeline for access logs too#10030
Merged
webmat merged 2 commits intoelastic:6.6from Jan 14, 2019
Conversation
jsoriano
pushed a commit
to jsoriano/beats
that referenced
this pull request
Jan 14, 2019
… ingest pipeline for access logs too (elastic#10030) (cherry picked from commit e05f967)
jsoriano
added a commit
that referenced
this pull request
Jan 21, 2019
…beat ingest pipeline (#10057) IIS logs can include zone ids when using IPv6, this is correctly parsed but geoip processor doesn't accept these addresses. Create a temporary field without the zone id to be used by geoip processor. (cherry picked from commit d59ae8c) (cherry picked from commit 5f1f6ca) (cherry picked from commit e05f967) Co-authored-by: Mathieu Martin <webmat@gmail.com>
leweafan
pushed a commit
to leweafan/beats
that referenced
this pull request
Apr 28, 2023
… ingest pipeline for access logs too (elastic#10030)
leweafan
pushed a commit
to leweafan/beats
that referenced
this pull request
Apr 28, 2023
…id in IIS filebeat ingest pipeline (elastic#10057) IIS logs can include zone ids when using IPv6, this is correctly parsed but geoip processor doesn't accept these addresses. Create a temporary field without the zone id to be used by geoip processor. (cherry picked from commit dad84e9) (cherry picked from commit 5f1f6ca) (cherry picked from commit e05f967) Co-authored-by: Mathieu Martin <webmat@gmail.com>
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
2 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 #10029 to 6.6 branch. Original message:
This is a manual backport, to fix an issue with the iis module, with regards to IP literals containing an IPv6 zone ID (issue #9836). This was fixed in master as part of the ECS conversion of the iis module (#9955).
Contrary to the fix in master, this fix is in line with Jaime's fix for the IIS error logs (#9869, #9932, #9933). This means the IP literal is saved as is to
iis.access.remote_ip(including the zone). This is fine, because this is a keyword field. The GeoIP processor then uses an IP literal with the zone stripped out, to avoid hitting the error. Note that this cleaned up field is not kept around in the 6.x line.