celery-exporter VS django-anymail

Since Celery tasks are executed outside of the Django context we need to monitor Celery separately from Django. I use Prometheus extensively, so much so that I wrote my own exporter for Celery metrics.

I would strongly suggest that you take a look at the django-anymail package. Using it will allow you to be able to swap between ESPs (if you are no longer please by their services) without having to refactor your code (switching packages/sdk). It has been a big time saver in a project of mine and the maintainer of the package responds quickly to any issues or questions you might have.

Once you switch to a transactional email service provider like mailgun, sendgrid or SES (as others have suggested), also take a look at the django anymail project: https://anymail.dev/ for a super seamless integration.

Popular answers include DRF, django-extensions, anymail, allauth and the DJDT.

I use django-anymail as the email backend. It hooks into Django and allows you to easily swap in and swap out different email providers. That way you're provider agnostic and can avoid vendor lock-in. Did Sendgrid hike their prices? Change three lines of code and use Amazon SES.