Configuring Uvicorn as started by "litestar run" to use structlog?

[livid leaf]

The structlog plugin works for well for most purposes -- but that doesn't extend to uvicorn itself, which despite having configuration that wraps both stdlib and structlog loggers with JSON, is emitting plain text.

In the pre-Litestar world, I used hypercorn --config ... to run my application with configuration from an arbitrary Python module. Now that I'm using litestar --app ... run, is there some equivalent?

[meager shoal]

Notes for Configuring Uvicorn as started by "litestar run" to use structlog?

At your assistance

@livid leaf

No Response?

If no response in a reasonable time, ping @Member.

Closing

To close, type !solve or byte solve.

MCVE

Please include an MCVE so that we can reproduce your issue locally.

[quaint nexus]

Have you configured the uvicorn loggers to use the queue_listener handlers?
https://github.com/litestar-org/litestar-fullstack/blob/main/src/app/config/app.py#L89-L98

[orchid charm]

src/app/config/app.py lines 89 to 98

"uvicorn.access": {
    "propagate": False,
    "level": settings.log.UVICORN_ACCESS_LEVEL,
    "handlers": ["queue_listener"],
},
"uvicorn.error": {
    "propagate": False,
    "level": settings.log.UVICORN_ERROR_LEVEL,
    "handlers": ["queue_listener"],
},