upgraded winlogbeat to v 5.a and not I'm not able to receive any data to logstash see below error on log stash
D:\Elastic\logstash\bin>logstash -f logstash.conf
io/console not supported; tty will not be manipulated
Settings: Default pipeline workers: 2
←[31mInvalid setting for elasticsearch output plugin:
output {
elasticsearch {
# This setting must be a boolean
# Expected boolean 'true' or 'false', got "True"
manage_template => "True"
...
}
} {:level=>:error}←[0m←[31mPipeline aborted due to error {:exception=>#<LogStash::ConfigurationError: Something is wrong with your configuration.>, :backtrace=>["D:/Elastic/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.4-java/lib/logstash/config/mixin.rb:134:in config_init'", "D:/Elastic/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.4-java/lib/logstash/outputs/base.rb:63:ininitialize'", "D:/Elastic/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.4-java/lib/logstash/output_delegator.rb:74:in register'", "D:/Elastic/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.4-java/lib/logstash/pipeline.rb:181:instart_workers'", "org/jruby/RubyArray.java:1613:in each'", "D:/Elastic/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.4-java/lib/logstash/pipeline.rb:181:instart_workers'", "D:/Elastic/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.4-java/lib/logstash/pipeline.rb:136:in run'", "D:/Elastic/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.4-java/lib/logstash/agent.rb:473:instart_pipeline'"], :level=>:error}←[0m
stopping pipeline {:id=>"main"}
The signal HUP is in use by the JVM and will not work correctly on this platform
This page contains a working example of what your Logstash configuration should look like for use with Beats.
As for your Winlogbeat configuration, those template options are not available when using the logstash output (they only work for the elasticsearch output). You must manually install the index template to Elasticsearch.
this is the result when I try to install the plugin.. it was previously working... should I remove log stash completely ?
D:\Elastic\logstash\bin>logstash-plugin install logstah-imput-beats
io/console not supported; tty will not be manipulated
Validating logstah-imput-beats
Plugin logstah-imput-beats does not exist
ERROR: Installation aborted, verification failed for logstah-imput-beats
For newer versions the plugin should already be included with Logstash. But in any case, you have a typo causing your problem: "imput" should be "input"
loaded that just now
D:\Elastic\logstash\bin>logstash-plugin install logstash-input-beats
io/console not supported; tty will not be manipulated
Validating logstash-input-beats
Installing logstash-input-beats
Installation successful
Did you delete the registry file used by Winlogbeat to persist it's read location? Try deleting C:/ProgramData/winlogbeat/.winlogbeat.yml to ensure there is data for Winlogbeat to read and send to Logstash.
Based on those logs, it appears to be successfully publishing events to the output. The end of the log that provides metrics about each output is cut off. There should be a metric tell you how many events were ACK'ed by Logstash.
Next step is to check Logstash's log files. You could also start Logstash in the foreground and run it with the debug flag to get some addition information logged to stdout.
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.