Include Django settings in report

[ziima]

We are trying to switch Django error emails for Sentry, but I noticed, the current Django settings are not recorded. Since they often provide clues for possible errors, it would be helpful to provide them also in Sentry.

[untitaker]

That makes sense but you know you can attach them yourself, right? https://docs.sentry.io/platforms/python/enriching-events/context/

On Thu, Mar 11, 2021 at 9:48 AM Vlastimil Zíma @.***> wrote:

We are trying to switch Django error emails for Sentry, but I noticed, the current Django settings are not recorded. Since they often provide clues for possible errors, it would be helpful to provide them also in Sentry.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/getsentry/sentry-python/issues/1052, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGMPRLKD7MIST55KA6LTCLTDB7WNANCNFSM4Y724KXA .

[ziima]

Yes, but it seems to me, it would be useful for Django projects in general.

[github-actions[bot]]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

[antonpirker]

Hello @ziima We are going to update the integration to support Django 4.0 in full and I think this Issue will then also be a good candidate to include in that update.

So sit tight.

[ziima]

@antonpirker Glad to hear that. :+1:

[sentrivana]

This is a lot of information to include in the payload for each event. Since there's a working way to do this on demand (https://github.com/getsentry/sentry-python/issues/1052#issuecomment-796777586) I don't think we need to add this to all events.