Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify integration with Celery when using Django #903

JeanFred opened this issue Nov 3, 2016 · 2 comments


Copy link

commented Nov 3, 2016


I am a bit confused by the documentation on how to use Raven with Celery in the context of Django.

The documentation states that « If you are also using Celery, there is a handler being automatically registered for you that captures the errors from workers. ». Which is quite cool!

However I have noticed that Celery-based errors come to Sentry with very little information − no stack-trace, no breadcrumbs.

Conversely, I have another Django app where (mainly for historical reasons) we registered Raven both in the Django configuration and using the Celery integration instructions − and the error reporting in Sentry is better. (But it might be for other reasons / configurations)

My question would be : is the handler automatically set via Django expected to be a fully-fledged integration, or is it a basic integration, and it is needed to also use the register_signal snippets to?

The docs could also use a short sentence making that clearer :)

Thanks !


This comment has been minimized.

Copy link

commented Nov 11, 2016

Gently upping this :) Would anyone have any idea?


This comment has been minimized.

Copy link

commented Nov 11, 2016

Hard to say since configurations vary a lot. So the best I can probably do is point you to how we use it ourselves in Sentry:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.