flower VS django-celery-results

Use flower to monitor workers and tasks.

Not sure what your criteria for good observability ist, but flower served me well enough for this in the last couple of years.

From experience i would not use threads for this or any background jobs. I would use Celery or Flask-RQ2 to be your workers, you will also probably end up using them to run other tasks as you encounter the need for other jobs. They both use Redis as a broker and job store and you can use Redis for other things like caching and so many other useful features. I kind of like RQ2 more then Celery because its a little simpler but Celery has a lot more to offer, more features. RQ2 has rq-dashboard for monitoring jobs and Celery has Flower.

The Celery package provides some number of (undocumented!) result backends to store task results in different local, network, and cloud storages. The django-celery-result package adds options to use Django-specific ORM-based result storage, as well as Django-specific cache subsystem.

To keep track of task result

The field is referenced in the docs here: https://github.com/celery/django-celery-results/blob/9b7deb464b0f3fa8c063a1cc70f9fc48829f9793/docs/includes/introduction.txt, and that appears to be accurate, but I don't have any experience with d-c-r personally so I can't really help much more. Hope you figure it out!

Hello, I have been having issues with Django and sending the results of Celery workers. Celery works and produces the results and if I set the backend to the redis server, it works fine. The issue is that Django ORM is not registering the TaskResults. I have tried everything under the sun in regards to configuration and I am sure that it's not the issue. I have found this Github: https://github.com/celery/django-celery-results/issues/102