Hi Michal, older versions of uWSGI seem to hijack Python's root logger and configure it its way. You can reset those settings and use your logger normally by getting the root logger and removing all handlers and filters. See my answer here for a working example:
http://stackoverflow.com/questions/34053273/python-logger-not-picking-up-the-configure-time-format/34062239#34062239 Cheers, Bastian Am 23.02.2016 um 16:29 schrieb Plovarna: > Hello, > I am in the process of Dockerizing my Python application. I would like > have container with uwsgi and my app behind. When somebody run > container, it will launch uwsgi in foreground mode and with the help of > nginx in other container I am able to communicate with my application. > > So far, so good. > > Next detail which I would like solve is logging. My idea is that stdout > output from Docker will contain mix of log messages from uwsgi AND my > application. I tried setup Python logging to StreamHandler (with > messages sended to stdout and also stderr), but uwsgi don’t reproduce it > on his stdout (I could se JUST uwsgi logs). > > My questions are: > > * Is it possible to setup uwsgi AND my Python app, that it will show mix > of both log messages? > * Is it possible to setup uwsgi AND my Python app, that it will show > JUST log messages from my application? > > Right now uwsgi logs are useless for me (I have access logs from Nginx > and I am missing logs from my app). I don’t want another piece of SW to > be installed inside of Docker container just because log juggling. > > Thank you for any hints > > Regards > Michal > > > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi > -- Dr. Bastian Venthur http://venthur.de Debian Developer venthur at debian org _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
