Mapper_parsing_exception in filebeat logs suddenly

Which filebeat version(s) are you running? This looks like a mapping conflict on the error field. This can be the case if filebeat 6.x is being run with a 5.x template mapping in Elasticsearch.

Check if you have multiple mapping templates, which will match filebeat. The mapping is versioned in newer filebeat versions. But old templates still match on filebeat-*.