what is the purpose of logstash-forwarder when logstash itself can ship files ?
I have a Usecase where my system might get restarted at times(killing all services abruptly),
when logstash-forwarder is restarted while reading a huge log file, how to implement state management?
(I assume, .logstash-forwarder is not updated while reading)
which has better state management logstash(with .sincedb) as shipper or logstash-forwarder (with .logstash-forwarder) as shipper?
But when I restart logstash-forwarder service while shipping a huge log file, its duplicating logs. Should I do any explicit configurations to handle this ?
Below is how my configurations look,
Logstash Config
input {
lumberjack {
# The port to listen on
port => 5544
ssl_certificate => "D:/logstash-forwarder/ssl/logstash-forwarder.crt"
ssl_key => "D:/logstash-forwarder/ssl/logstash-forwarder.key"
type => "Logs"
codec => plain { charset => "UTF-16" }
}
}
LSF stores the state information in .logstash-forwarder, i.e. a file in the current directory. Is that file ever created for you? Are you starting LSF from the same directory both times?
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.