Hi all,
I'm sending windows logs via winlogbeat (v.7.13.2) to a logstash instance (v.7.13.0), which processes the logs and sends them to an ES index "winlogs" (v.7.13.0). I've set up the pipeline (no logstash filter yet implemented) following the quick start manual and since I'm sending logs to logstash I've manually inserted the template using the alternate method listed here.
I've noticed that the service doesn't send logs to Logstash -> ES the same way as a command line call "./winlogbeat.exe -e". Via the command line call, thousands of docs land in the index, whereas the service results in only a few dozen.
Can someone explain to me the difference? I was expecting the same behavior (all logs up to an ignore_older variable) from both the Command Line and Service implementation. Can one setup the service to run the same as the command line?
Here my configurations:
winlogbeat.yml
winlogbeat.event_logs:
- name: Application
ignore_older: 72h
- name: System
ignore_older: 72h
- name: Security
ignore_older: 72h
output.logstash:
hosts: ["127.0.0.1:5044"]
setup.template.enabled: false
setup.template.overwrite: false
setup.ilm.enabled: false
logstash beats config
input {
beats {
port => 5044
}
}
output {
elasticsearch {
hosts => ["http://localhost:9200"]
index => "winlogs"
}
}