- Version: filebeat latest build from master branch, CRI-O latest build from master branch.
- Operating System: CoreOS
- Discuss Forum URL:
- Steps to Reproduce:
Filebeat doesn't collect logs generated by CRI-O since they are in /var/log/pods/<pod uid>/<container name>/<index starting with 0>.log. I've created this issue and looked at cri-o code and it has no options to change the path. It accepts it from kubelet and does as kube decides.
I've checked filebeat code, but the way it derives path is pretty complex unless someone can guide me and I can create a pull request. 1st thing I need is how to get a Pod UID (not ID). It looks like they are disabled by default, then I need to get a name of a container and where to use both of them to generate new path to the log.
Filebeat doesn't collect logs generated by CRI-O since they are in
/var/log/pods/<pod uid>/<container name>/<index starting with 0>.log. I've created this issue and looked at cri-o code and it has no options to change the path. It accepts it from kubelet and does as kube decides.I've checked filebeat code, but the way it derives path is pretty complex unless someone can guide me and I can create a pull request. 1st thing I need is how to get a Pod UID (not ID). It looks like they are disabled by default, then I need to get a name of a container and where to use both of them to generate new path to the log.