2017/07/06 08:42:36.608751 metrics.go:34: INFO No non-zero metrics in the last 30s
2017/07/06 08:43:06.608836 metrics.go:34: INFO No non-zero metrics in the last 30s
2017/07/06 08:43:36.608856 metrics.go:34: INFO No non-zero metrics in the last 30s
host field doesn't seem to be the same? You have 54.26.43.27 in logstash and 52.24.17.29 in filebeat. Also I think there is a spurious " in the host for logstash conf
Hi @exekias for filebeat i use ip: 54.26.43.27 and for logstash i use: 52.24.17.29. I'm sorry i've missed the second spurious but there is. I use for filebeat and logstash two different virtual machine.
Thanks for replay
host field is the IP address to listen on, it's optional so if you don't define it, it will listen in all interfaces. If you define it you must definitely use logstash node IP, not filebeat's
Please check if that fixes your issue, I think it should
Hi @exekias it isn't the config but policy question of my machine so i decided to do the first try without logstash.
But when i try load data in elasticsearch give me error.
The filebeat.yml:
following the documentation send me this error. Can you help me?
2017/07/11 08:18:10.252056 metrics.go:34: INFO No non-zero metrics in the last 30s
2017/07/11 08:18:40.251944 metrics.go:34: INFO No non-zero metrics in the last 30s
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.