Is there a good strategy to read an entire file as the "message" value you would send to ElasticSearch?
I see "read" mode as part of file input plugin but that wants me to write the input to a different file. I want to take what I've read and push it to Elastic Search.
I tried using the codec for multiline but didn't know how to use the end of file as the pattern.
The system i'm trying to parse writes a new file for every error so the whole file is what I need to consume. A new error, writes a new file.
Brilliant!!! I was trying to attack it with a pattern that always matched. I also think the fact that I wasn't using the auto_flush_interval attribute was causing some sort of issue.
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.