Configure Celery to log using the Pulp syslog handler
In The 2.y line Celery uses a signal to install the logging handler inside of Celery processes. We need to port the installation to 3.0. The signal handler itself has already been ported to 3.0-dev and now lives here.
The signal handler on the 2.y line was imported with this line. Note that pulp.server.async.app is now pulp.tasking.celery_app so the noqa import should occur there.
#11 Updated by bmbouter about 4 years ago
- Checklist item test logging from pulp_celerybeat added
- Checklist item test logging from pulp_resource_manager added
- Checklist item test_logging from a pulp worker added
- Checklist item remove pulp.app.logs and any imports+comments referencing it added
I'm adding some checklist items to this.
Note that we had written a custom logger which on 3.0-dev is current housed at
I wrote this story originally to configure the logger at pulp.app.logs, but from the PR posted I think replacing our custom logger with the Django logger itself may be better. I would be very surprised if our custom logger was better than the Django logger.
See this related convo: https://github.com/pulp/pulp/pull/2862/files#r89887158
Please register to edit this issue