Now at product env. When I restart es(filebeat is still running), I will meet an issue that filebeat doesn't send the log info to es. one line log is too large(7K) may cause this issue?
What do you see in the logs or std out to denote filebeat is unable to send to ES?
Has the output to elasticsearch such as host and port been uncommented and set correctly?
logs don't denote some errors. And output setting is correct. Filebeat send new access logs with small size successfully. I think less max_retries may be this issue's reason, I will set max_retries a large number, hoping that works.
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.