Filebeat will collect logs from all namespaces, the message you are seeing is talking about the pod/namespace where filebeat is running, this is part of the initial discovery and configuration.
@Alex_Scoble
Thanks for your input.
So to query against annotation one must include them, I guess that makes sense.
I'm still having issues with actually getting logs to flow through, it seems like the autodiscover does not discover new events as they occur. I've experimented with different namespaces etc. But no success, my config is the one above. I also verified connection to logstash from minikube. (10.0.2.2:5044), so I'm pretty sure I just lack a working configuration.
(WIth the filebeat config above) They don't show anything. I'm experimenting with minikube on the one end, and I have a docker ELK running on my laptop.
So i'm sending filebeat logs to 10.0.2.2:5044, (I'm able to telnet at it and get an error output from logstash, so I have the necessary ports open). Link to logs
These logs are after restarting filebeat and restarting multiple applications, it seems like the harvester not fetching them at all.
I'll be trying on a test cluster later to debug even further.
Of course I might have missed the point about autodiscover with hints, but the kubernetes autodiscoverer worked so well with templates configured.
Thanks alot for pointing them out.
About debugging the configuration; do you have any tips to doing that? I tried using debug flags, but I found it difficult to find errors in the logs.
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.