Best practice to increase memory for containerized logstash

We are running logstash within a Docker Container to monitor RabbitMQ. Due to some huge messages we have to increase the memory with which logstash is operating.

According to we can do this via changing properties within the file jvm.options. In our situation (we provision our machines with Ansible) this has the drawback that we are delivering a lot of other properties with this file - and maybe loose some changes in this file in the future due to it doesn't get updates on increasing logstash versions.

On searching for an environment setting I found LS_HEAP_SIZE => which sounds promising. But in it looks the "official" way seems to be the one with the config files.

So the question is: Is the environment property LS_HEAP_SIZE an "official" way of increasing logstash memory in this deployment scenario?

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.