1428086 - Track Celery task errors in Sentry, not via email

Status: RESOLVED WONTFIX

(developer.mozilla.org Graveyard :: General, enhancement, P2)

Description

[John Whitlock [:jwhitlock]]

What feature should be changed? Please provide the URL of the feature if possible.
==================================================================================
With the setting CELERY_SEND_TASK_ERROR_EMAILS = True, errors in tasks are sent as traceback emails to admins. Instead, the tracebacks should be tracked in Sentry, where application tracebacks are tracked.

What problems would this solve?
===============================
Celery traceback emails have several issues:

- There is no long term tracking of issues, or frequency counts of events
- A single issue, such as a rebooting database, can result in 10 - 1000 emails, encouraging admins to filter and ignore all emails
- Emails to admins caused us to exceed email quotas (bug 1421016), potentially impacting deliverability of MDN user emails

Sentry is a better tool for tracebacks

- Issues are combined, counted, and tracked over time
- Multiple events are aggregated with a single email to admins

Who would use this?
===================
MDN Admins

What would users see?
=====================
No more celery traceback emails

What would users do? What would happen as a result?
===================================================
Issues would be tracked in Sentry, not email

Is there anything else we should know?
======================================
Sentry docs for integrating with Celery:

https://docs.sentry.io/clients/python/integrations/celery/

It may require changing to the standard Celery / Django configuration first (bug 1268277)

Comment 1

[BMO Automation]

MDN Web Docs' bug reporting has now moved to GitHub. From now on, please file content bugs at https://github.com/mdn/sprints/issues/ and platform bugs at https://github.com/mdn/kuma/issues/.