On Thu, Sep 1, 2016 at 2:12 AM, Jan <[email protected]> wrote:
> Found the error. In my original pipeline-rule I used the "to_ip" function > to convert the pattern match to an IP. With this setting resolving the IP > to a geo location fails. > I changed the rule now to convert the pattern match to a string by using > the "to_string" function. Voila... geo location works for all custom fields > now. > (to Graylog devs). That's a bug isn't it? I mean, what's wrong with assuming an IP address is an IP address? Shouldn't the GeoIP processor support both string and "ip" fields types? -- Cheers Jason Haar Information Security Manager, Trimble Navigation Ltd. Phone: +1 408 481 8171 PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1 -- You received this message because you are subscribed to the Google Groups "Graylog Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/CAFChrgJFzC5HFDnX2c1soixC_7LH5n%3D2-MEiymEp88GQeUHhuw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
