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 ? several springboot rest api containers behing nginx containers with the same configuration (logs configuration is the same:same path).several nginx containers in load balancing with the same configuration (logs configuration is the same: same path).Which pattern should I use to push my logs using filebeat to logstash if I have the following configuration: This works fine but when it comes to scale out nginx and springboot container, it is a little bit more complex for me. a filebeat container also mounting the dedicated logs volume.a tomcat / springboot container which mount the dedicated logs volume.a nginx container which mount the dedicated logs volume.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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |