IP grok pattern correctly parses IPv6 addresses with zone ids, but if these addresses are used with the geoip processor it fails with errors like '::1%0' is not an IP string literal..
To avoid confusion I think that geoip module should accept zone ids, even if they are not relevant in this case and ignored.
Seen in elastic/beats#9836
IPgrok pattern correctly parses IPv6 addresses with zone ids, but if these addresses are used with the geoip processor it fails with errors like'::1%0' is not an IP string literal..To avoid confusion I think that geoip module should accept zone ids, even if they are not relevant in this case and ignored.
Seen in elastic/beats#9836