gunicorn worker (uvicorn.workers.UvicornWorker) does not report request/s via statsd client

[sileht]

Hi,

gunicorn worker (uvicorn.workers.UvicornWorker) does not report request/s via statsd client, like other gunicorn workers.

Regards,
Mehdi

Important

• We're using Polar.sh so you can upvote and help fund this issue.
• We receive the funding once the issue is completed & confirmed by you.
• Thank you in advance for helping prioritize & fund our backlog.

[Traktormaster]

Hi!

I've just ran into this issue myself. After delving a bit into the codes of gunicorn and uvicorn, I can say the problem is simple, but not very trivial to fix.

The gunicorn statsd implementation is mixed with their logging facility. Which is a a little questionable, no wonder they have an issue to refactor it. Since uvicorn has its own logging system and does not reuse the logger instance from gunicorn (even though it inherits it by forking), the statsd codes are never invoked.

I could not find an easy and nice way to make it work. The worker.log object would need to be accessible from the running http protocol, and even then the statsd logging could not be reused as-is since it's merged with the real logging. (it could lead to logging twice I think)

Anyways, depending on what you're using this can be circumvented in the framework level. I'm using Starlette and there is an ASGI middleware to send request metrics to statsd.

I know this is not a solution, but I wanted to write it down for future reference. Maybe someone will find it useful.

[sandys]

im facing the same issue here. is there a workaround ? we are using fastapi

[damluji]

Any updates please? ran into the same problem today.

[Kludex]

Given that Gunicorn has the issue benoitc/gunicorn#1564, and we are deprecating the workers within Uvicorn (#2302).

• Feel free to recreate this issue on https://github.com/Kludex/uvicorn-worker