Celery Task throws option is ignored by receiver_task_failure signal.

[meunomemauricio]

In Celery, it's possible to specify a tuple of exceptions in the throws option. This allows us to mark a task as Failed but only log it as INFO, not ERROR.

This is how it's handled on Celery:

https://github.com/celery/celery/blob/1c955bf76a9a33052d87f2bccf0889fb21f27d41/celery/app/trace.py#L131-L141

https://github.com/celery/celery/blob/1c955bf76a9a33052d87f2bccf0889fb21f27d41/celery/app/trace.py#L233-L258

But this functionality is being ignored in the receiver_task_failure signal, which always log it as an exception:

django-structlog/django_structlog/celery/receivers.py

Lines 58 to 61 in 1b48490

	def receiver_task_failure(
	task_id=None, exception=None, traceback=None, einfo=None, *args, **kwargs
	):
	logger.exception("task_failed", error=str(exception), exception=exception)

I wonder if there's a way to work around this. I really like the throws functionality.

[jrobichaud]

Fixed in 2.1.3. Let me know if it does not suit your needs.

I did like in Celery's documentation: Log as info and no traceback.