We are using the Elastic Cloud hosted solution on AWS at version 6.6.1. We are using filebeats 6.6.0 and the IIS module to parse IIS 10 logs into Elastic Search.
When we look at the logs page we are seeing many
failed to format message from c:\inetpub\logs\Logfiles\W3SVC3\u_ex190220.log
the message you're seeing stems from the fact that the Logs UI didn't properly support the docs created by filebeat's IIS module. This has been fixed in Kibana issue #30398 and will be part of the 6.7 release of the Elastic stack.
If you are looking for a quick workaround until then, you could adjust the ingestion pipeline to not delete the message field during ingestion. The pipeline should be called something like filebeat-6.6.0-iis-access-pipeline and can be read or written using the ingest pipeline APIs.
Please let me know if you require more assistance with that. I apologize for the inconvenience this has caused.
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.