Propagate Gunicorn Uvicorn worker logs

[br3ndonland]

Description

The Uvicorn worker class originally disabled propagation because it resulted in duplicate logs if enabled (Kludex/uvicorn#614, Kludex/uvicorn#623). As the docs on logging.Logger.propagate explain, "If you attach a handler to a logger and one or more of its ancestors, it may emit the same record multiple times."

inboard/inboard/gunicorn_workers.py

Lines 54 to 62 in 68ceb47

	logger = logging.getLogger("uvicorn.error")
	logger.handlers = self.log.error_log.handlers
	logger.setLevel(self.log.error_log.level)
	logger.propagate = False
	logger = logging.getLogger("uvicorn.access")
	logger.handlers = self.log.access_log.handlers
	logger.setLevel(self.log.access_log.level)
	logger.propagate = False

Instead of disabling propagation and keeping Gunicorn handlers set on the logger, another solution is to remove the Gunicorn handlers and enable propagation so the root logger can manage all logs (#131). This would be closer to the intent expressed in the current logging docs: "Uvicorn, Gunicorn, and FastAPI log streams are propagated to the root logger, and handled by the custom root logging config."

Changes

This PR will update the Gunicorn Uvicorn worker to remove handlers from uvicorn.error and uvicorn.access and instead propagate those log records to the root logger. This will avoid duplicate records and ensure the root handler applies the configured formatter and filters.

Related

• I have reviewed the Guidelines for Contributing and the Code of Conduct.
• Resolves Logging config not applied for uvicorn in gunicorn #131
• Duplicate logs when using root logger with 'gunicorn -k uvicorn.workers.UvicornWorker ...' Kludex/uvicorn#614
• Don't propagate logs to parent loggers in Gunicorn worker Kludex/uvicorn#623
• Python 3 docs: Standard Library - logging - logging.Logger.propagate

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
inboard	Ready	Preview	Aug 1, 2026 4:19am