Re: Logging of full trace with Debug set to False

Hi!

Seems like things were improved since then:

https://docs.sentry.io/platforms/python/celery/

There is an integration that I can enable which should take care of things.

I realy like Sentry. Currently I use the free tier while I check how to setup my own node.

Some of my Apps already send Exceptions (broke some things to test it).

Thanks for the hint to this excellent tool!

Kevin

Am Montag, 28. Januar 2019 13:55:29 UTC+1 schrieb Michal Petrucha:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On Mon, Jan 28, 2019 at 04:45:44AM -0800, Kevin Olbrich wrote:
> Hi Anirudh,
>
> I am using uWSGI and not Gunicorn. At least for uWSGI, with Debug = False,
> it only logs the HTTP status code but not exception (might be the same with
> Gunicorn).
> I will try Sentry which provides a clean GUI and notification of new
> problems. This also seems to work for my Celery tasks and Django admin
> commands.

Since you're mentioning Celery, I thought it might be worth mentioning
that Celery performs some black magic ritual on the Python logging
config in its default configuration, which interferes with the way
Sentry handles errors – or at least that's been my experience. At one
point I noticed that errors happening inside Celery tasks didn't have
all the stack values, like ones from the regular request/response had.
I don't remember exactly how, and I don't have access to that code
base anymore, but I remember that we had to explicitly disable as much
of Celery's custom logging as we could in order to get that to work.
(Might be that things have improved since then, though.)

Good luck,

Michal
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJcTvuFAAoJEHA7T/IPM/kltD8P/0MfET5/KylfZM/BWHDz4+vn
8U7hr4Zraz5R+zzr4yq7Ow0tom4zWE0EqpYREv87A4tX7dHGITTQLbU+bCce/MNQ
tIVD2D498XsEBGRsNav0kOr6ATuWoPuJlLLSFYGbGHedCKz6UB+ftmwYhL7WOQgr
zE8LeLS37jbm02/z6DD25intYUpRbKeeSRjyqkc+6esUz2IAXVQQ1NcUtJjPbmvi
zJtyWUX/RXS3Wulrp8lwLJ7rThcFAh3wVmC/nJCHeBQFLDmmLZx08EEnV1w7uxwv
AcowzfrGPOYv7VcOK9K9KvUPCrIj3KovU4DPlffuX6xxy8FZTvIyDptJAaMnh9C+
i8So48kPL1TxBk1lPuWx8TLr+RR1y4LIy7KVwMgRyeFC5zGIdBiAFIwo9X5utdc9
1uuO07bGn9224vpk87zyizA8Q88Qeee7kco+a0v0f8+Xxz6oAKg9uf3broJ9nl99
jp6Pp9QTzlpYFnw0bjMDMI3KRLkAxbWmeuGtBt7tELKFfHoae3RtfCqNitvEhN07
rz44xC2dbwPvQdV2UMElX+jS9omk+8oEwgMNvOPXyAsf3NexwcuN0lzoo5MS2OpY
kkwbNCD0aeHtreY5BJrXgONmXd58OswZhsCbcvZXqhIJ1MxreCzasXVvF7ZNHp6z
daRHSphHWV6/sDLFFfGw
=6WLZ
-----END PGP SIGNATURE-----

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/bac79f70-487f-45dd-9d66-c9f397cb3785%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.