i am fairly new to this... and i am stuck... just installed my ELK stack... filebeat seems to working fine... but i moved on to metricbeat i get this error in Kibana when trying for example to select "metricbeat-*" under "discover"
Fatal Error:
Courier fetch: Bad Gateway
Version: 6.4.0
Build: 17929
when i load the
[[Metricbeat System] Overview]
Dashboard it starts to visualise and then switches to the same Fatal Error.
what might be the problem? where can i try to find out more about it?
I'm getting that, too. I just updated metricbeat to 6.4 and I'm only getting this from the metricbeat index. I can view other indexes (audit beat, filebeat, etc.) fine.
This makes the second consecutive metricbeat update that's broken my system...I think I'm going to stop updating for a while until things settle down with it.
I'm experiencing the same issue 'Courier fetch: Bad Gateway' as well as just with querying my metricbeat index, but I am not using nginx. I am using haproxy. Anyone know how I can set those limits in haproxy?
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.