I am aware that one should use a tracker store to log conversations, but I am wondering what I should do with the logs that normally get routed to the rasa_core.log file. Trying to deploy to AWS, we noticed that saving logs to files is a really bad practice while using container orchestration since pods come and go, and so do the files that come with them. So ideally these files should only be read, not written (such as configuration files).
For tracker stores, this is not a problem since one can use Mongo, Redis and they can be subclassed to be customized. But what solutions have been tried out there when it comes to the logs going to rasa_core.log? I am open to anything, because right now I am just “not logging” to make it work (quite literally) and this will become painful really, really soon.