Becoming increasingly frustrated using Logstash for the simple need of a line number when there is an error occurs when reading the configuration. The move from 1.6 to 2.0 has been anything but painless.
Error meanings are almost on the level of Microsoft. Something happened, but you got to pull everything apart to find out what happened. Also experiencing the error below which is extremely useful.
retrying failed action with response code: 429 {:level=>:warn}
The main issue is when there is a error in the configuration, to put in the line number on which the configuration failed, so you don't have to try and guess were the problem occurred.
Error: Expected one of \", ", any character at line 81, column 1 (byte 2412) after output {
#stdout {
# codec => "rubydebug"
#}
elasticsearch {
index => "public_toilets"
manage_template => "false"
}
stdout {
codec => "dots
}
}
You may be interested in the '--configtest' flag which you can
use to validate logstash's configuration before you choose
to restart a running system.
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.