Page MenuHomeSoftware Heritage

Activate gunicorn's statsd monitoring for objstorage services
Closed, MigratedEdits Locked

Event Timeline

douardda renamed this task from Actiave gunicorn's statsd monitoring for objstorage services to Activate gunicorn's statsd monitoring for objstorage services.Mar 21 2019, 9:53 AM
douardda triaged this task as High priority.
douardda created this task.

Status:

Tryout with douardda and I failed so far.
After setting the right logger in the configuration, it actually started logging but only workers event (gunicorn.workers: number of workers managed by the arbiter - gauge).
Tried to dig in in the code but did not find the right solution yet.

There are apparently compatbility issues with the gunicorn workers we use (aiohttp) and gunicorn to send the information we are interested in (gunicorn.requests*).
Well, at least with a default setup [1]

This still needs further investigation.

[1]
https://github.com/benoitc/gunicorn/issues/1300
https://github.com/aio-libs/aiohttp/issues/705
https://github.com/aio-libs/aiohttp/pull/1117

Something is fishy somewhere.
We tried [1] and did not notice that behavior.

https://docs.aiohttp.org/en/stable/logging.html#gunicorn-access-logs

And to be thorough, @douardda checked back on his machine and the behavior is correct there (even with the same version as the production).