Set up Sentry error reporting
Opened this issue · 5 comments
But make it optional, because a developer might not have an API key for that platform during local development. 🙂
Is it possible to use something like indexed debug symbols with Perl/Sentry, so that each stacktrace is directly attributed to the correct source commit?
Is it possible to use something like indexed debug symbols with Perl/Sentry, so that each stacktrace is directly attributed to the correct source commit?
To answer my own question, Sentry seems to send the source by itself: getsentry/perl-raven#32 We should just ensure that release is set to the correct source commit during deployment.
great 👍
This issue has been open 90 days with no activity. Can you give it a little love by linking it to a parent issue, adding relevant labels and projets, creating a mockup if applicable, adding code pointers from https://github.com/openfoodfacts/openfoodfacts-server/blob/main/.github/labeler.yml, giving it a priority, editing the original issue to have a more comprehensive description… Thank you very much for your contribution to 🍊 Open Food Facts