![ship nginx access logs through filebeats ship nginx access logs through filebeats](https://www.outcoldman.com/en/archive/2021/01/14/analyzing-aws-amplify-access-logs-part-1/datagrip-numbers.png)
In the second proposal, how to scale filebeat ? (having the name of the container in the filename of the logs?) and having only one filebeat container ? Should I create a global log volume shared by all my containers and have a different log filename by container Should I create one volume by set of nginx + springboot rest api and add a filebeat container ?
![ship nginx access logs through filebeats ship nginx access logs through filebeats](http://help.shipgear.com/4/macola_psql/fdxsms.gif)
![ship nginx access logs through filebeats ship nginx access logs through filebeats](https://www.webhostinghub.com/help/images/stories/cpanel/cpanel-raw-access-logs-download-ftp.jpg)
Over what I have read over Internet, we could have the following setup: One nginx per container and one tomcat per container, meaning we can’t have an additional filebeat within a nginx or tomcat container. In the container strategy, a container should be used for only one purpose. I’m looking for the appropriate way to monitor applicative logs produced by nginx, tomcat, springboot embedded in docker with filebeat and ELK.