Documenting gunicorn logging in Flask?

[pamelafox]

I was wondering what you think of adding a section to the gunicorn docs page about logging. This seems to be the standard approach, and worked for me:
https://trstringer.com/logging-flask-gunicorn-the-manageable-way/

Specifically:

if __name__ != '__main__':
    gunicorn_logger = logging.getLogger('gunicorn.error')
    app.logger.handlers = gunicorn_logger.handlers
    app.logger.setLevel(gunicorn_logger.level)

It took some time to find that, however, and its not obvious from the gunicorn docs. I'm happy to draft a section if it seems like a good idea (and if that is indeed the best path).

[davidism]

I'm not really clear that it's a good idea to take all Gunicorn's logging handlers/levels and use them for Flask too. Typically you'd configure everything (Flask, Gunicorn, etc.) using logging.config.dictConfig ahead of time, not take Gunicorn's already-configured stuff and overwrite Flask's. That pattern is already shown in https://flask.palletsprojects.com/en/2.3.x/logging/, it's not Gunicorn specific.

So basically, that blog kinda got it right, it shows configuring Flask loggers before creating the app. But it went off in the direction of copying other config rather than performing a full configuration, when it could have gone all in on configuring one root handler, for example

[pamelafox]

Okay, that's great to know. I'm trying to write samples that use Flask best practices, so I'll follow your suggestion, which works as well. The shortest version is probably:

logging.basicConfig(level=logging.DEBUG)

I'm putting that behind a guard so that it is only set in development to DEBUG level.

So I guess it doesn't warrant a section on the Gunicorn article, since it's no different than setup otherwise, but it's interesting how many articles/SO posts I found about the topic. Perhaps folks will now find this discussion, too :)