In the Kubernetes world, one of the most popular choices for an ingress controller is the nginx-ingress-controller, which doesn't use a standard Nginx log format though. Instead, it uses a custom format, documented here: https://github.com/kubernetes/ingress-nginx/blob/master/docs/user-guide/nginx-configuration/log-format.md
Given how many projects use this ingress controller, it would be nice to add a module called nginx-ingress-controller and make things work for people out of the box instead of every projects having to clone the nginx module. Or maybe add some kind of option to the nginx module to support this de facto standard in the Kubernetes world format instead.
I think this will greatly improve the adoption of Filebeats within the Kubernetes ecosystem!
In the Kubernetes world, one of the most popular choices for an ingress controller is the nginx-ingress-controller, which doesn't use a standard Nginx log format though. Instead, it uses a custom format, documented here: https://github.com/kubernetes/ingress-nginx/blob/master/docs/user-guide/nginx-configuration/log-format.md
Given how many projects use this ingress controller, it would be nice to add a module called nginx-ingress-controller and make things work for people out of the box instead of every projects having to clone the nginx module. Or maybe add some kind of option to the nginx module to support this de facto standard in the Kubernetes world format instead.
I think this will greatly improve the adoption of Filebeats within the Kubernetes ecosystem!