The log line looks like this (it's got from our app, then processed by Filebeat):
2018-10-08 13:39:36,247 INFO - {"a": "b"....}
But, sometimes our app throws loglines which aren't JSON:
2018-10-08 08:54:18,592 INFO - user 10470684 cannot assume zuid 10470684
In this case pipeline fails, but if this log line doesn't appear in EFK, this is not the problem. The problem is that ingesting is completely stopped, and I need to restart Filebeat.
Now I skip that lines in Filebeat config, but I can't figure out if I add all problematic lines to its config. I would like to:
just skip line if it's not JSON
or (better but not mandatory), add it as-is (like "message": "my logline"), if it's not JSON
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.