{"type":"mapper_parsing_exception","reason":"failed to parse field [network.forwarded_ip] of type [ip] in document with id 'msD2cIUBIsfwhIgCSPy9'. Preview of field's value: '0'","caused_by":{"type":"illegal_argument_exception","reason":"'0' is not an IP string literal."}}, dropping event!
it's strange that it's ingesting 0 in an IP-mapped field.
I was just checking a spike in logs and they were full of this event. I haven't modified any mappings or anything like that. I guess this might be due to the update from 8.2 to 8.5 coz that's when issues started occurring.
Can you please tell me how can I fix this issue or how can I set the data type to keyword or string so that the error stops and the document shows proper information and does not drop the event?
the entire event is shown in the message field followed by
Cannot index event publisher.Event{Content:beat.Event{Timestamp:time.Date(2023, time.January, 4, ********
*****full event************
{"type":"mapper_parsing_exception","reason":"failed to parse field [network.forwarded_ip] of type [ip] in document with id 'orWAe4UBIsfwhIgCi1lm'. Preview of field's value: '921'","caused_by":{"type":"illegal_argument_exception","reason":"'921' is not an IP string literal."}}, dropping event!
p.s. I'm using Elastic agent not any particular beat
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.