How to configure Gunicorn logs to output to a defined directory and rotate log files?

[stgztsw]

superset 6.0.0rc1
docker compose -f docker-compose-non-dev.yml up

Gunicorn logs are only output to standard output. I want them to be output to a specified directory and mounted to the host machine. How should I adjust this?

00:00:00 /app/.venv/bin/python3 /app/.venv/bin/gunicorn --bind 0.0.0.0:8088 --access-logfile - --error-logfile - --workers 1 --worker-class gthread --threads 20 --log-level --timeout 60 --keep-alive 2 --max-requests 0 --max-requests-jitter 0 --limit-request-line 0 --limit-request-field_size 0 superset.app:create_app()

[dosubot[bot]]

You can configure Gunicorn in Superset's Docker Compose setup to write logs to a specific directory by setting the ACCESS_LOG_FILE and ERROR_LOG_FILE environment variables to absolute file paths, such as /app/superset_home/gunicorn-access.log. These variables are picked up by the entrypoint script that launches Gunicorn in the container. To persist and access these logs on your host machine, mount the superset_home volume (used at /app/superset_home in the container) to a directory on your host in your docker-compose-non-dev.yml file.

Gunicorn itself does not handle log rotation, so you'll need to use an external tool like logrotate on the host or a sidecar container to manage log rotation for these files. For reference, see how the log file paths are set via environment variables in the entrypoint script here and how volumes are mounted in the Compose file here.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}