There was a big spike of these recently:
which I think isn't that big of a deal, except the error parameter was unset:
(link)
Or maybe this is the thing where the same field name is used with a different type for different log entries, and Logstash is unable to handle that?
In any case, it's something to be fixed in the logging code and should be looked into.

