Add Sentry reporting for exceptions on production instance #770

Activity

1. mxsasha

   added this to the v1.7 milestone on Oct 20, 2022
2. mxsasha

   self-assigned this

   on Oct 20, 2022
3. mxsasha

   added

   infrastructure-dockerIssues related to the underlying infrastructure of the project as well as containerizationIssues related to the underlying infrastructure of the project as well as containerization

   on Oct 20, 2022
4. baknu commented on Nov 8, 2022

   

   baknu

   on Nov 8, 2022

   Contributor

   More actions

   We might also want to ask Prolo if they could provide us with Logstash (instead of using an external service like Sentry).
5. mxsasha commented on Nov 9, 2022

   

   mxsasha

   on Nov 9, 2022

   CollaboratorAuthor

   More actions

   Logstash is a rather different product. Sentry can be self-hosted too though.
6. mxsasha

   added a commit that references this issue on Nov 10, 2022

   Fix #769 - Correctly indicate probe error to user (#802)

   ...

   10ec9b0
7. mxsasha

   added a commit that references this issue on Dec 13, 2022

   [1.6.x] Fix #769 - Correctly indicate probe error to user (#802)

   ...

   66abd12
8. mxsasha

   added a commit that references this issue on Dec 20, 2022

   [1.6.x] Fix #769 - Correctly indicate probe error to user (#802)

   ...

   0ce0690
9. mxsasha

   added a commit that references this issue on Feb 9, 2023

   Fix #770 - Add Sentry support

   ...

   This issue will close once commit 2585447 is merged into the 'main' branch.

   2585447
10. mxsasha

    closed this as completedin 1a15c19on Feb 9, 2023
11. stitch

    added a commit that references this issue on May 4, 2025

    Fix internetstandards#770 - Add Sentry support

    ...

    This issue will close once commit 1a15c19 is merged into the 'master' branch.

    1a15c19