Gravitee AMpersists "everything" is mongodb, see ccc
elasticsearchthat belongs to gravitee stack, and load it into the separate Monitoring dedicated Elastic Stack,
Gravitee AM, and there is a MongoDB Connection error : maybe I am wrong, but then I think your
Gravitee AM, is completely usable (you can't do anything with it)
Gravitee AMkeeps growing in resources usage, i htink :
Gravitee AM, until you fixed the MongoDB connection issue, and then respawn
# edit soruce code, git commit n push it # taer down git pull source code updates, respawn it all docker-compose down --rmi all && git pull && docker-compose up -d
For now, we are in the test so we shut down and correct the issue if there is one but if it happens in production ( we will run it on production in one week I think) and since all the application is in the same VM if it crashes on the weekend it's not good hh :D.
The solution will be to run Gravitee AM in his own VM but it will be nice if it doesn't crush the VM every time the Mongo cluster has issues. :)
The scenario will not happen in production but we never know.
Since Gravitee AM don't manage levels of logs like Infos errors ... it's not possible to do what I want to do.