If importing json via the file plugin, and your json has a field in it called "path", then logstash overwrites it with its own "path" value (for the log location)
Could it not call the new field @path or similar? Or back up the existing "path" field before overwriting it?
I see similar issues with the host field, though it doesn't overwrite. I would haveover like to be able to filter on whether the incoming json had a host field or not, and am unable to.
What should be the correct logstash way of resolving this?