As someone of you that is already using celery already know extend the celery logger was a bit tricky until the last version, mainly because the logger object is not unique, the same handler is added to different logs object (Main Process logger, PoolWorker logger, TaskLogger).
For this reason the command logging.getLogger(“Celery”) give you back only the Main Process logger.
From the version 2.2.7 of Celery is possible to extend all the logs object by using two new signals after_setup_logger and after_setup_task_logger.
celery
Europython 2011: Playing tasks with Django Celery (Video and slides)
A simple python sandbox for Celery and not
At the end of this post you will find the source code of a python sandbox that I write for have a general sandbox that work for all my celery tasks.
Anyway this is a general python code and you can use it also without Celery but here I will give you also some example to how to use it in easy and fast way with Celery.Read more
Run Celery tasks from PHP
If you are reading this article probably you already know what is Celery but for who think that it is something to eat I will give you a definition.
Celery is an asynchronous task queue/job queue based on distributed message passing developed in python.
If your using Celery for your back-office tasks will be very nice to run some tasks after an action performed on the front end of your web site, like an user action.
If your web front end is wrote in PHP there is an easy and useful way for do it trough Rabbit MQ, the message broker used by celery.Read more