Use an exception reporter

[Sebastian-ubs]

User Story As a developer I want to be informed about errors and exceptions early so that I can see issues and fix the code soon. As a developer I want to be able to collect errors and exceptions from other devs and testers, so that I can reproduce and find bugs that do not appear visually or only in rare conditions. As a developer I want to be able to have an automated way of collecting exceptions so that I can support users efficiently.

Description Have a tool (maybe running as a separate process launched by Platform/PT10) that would report issues and exceptions back to a common place, e.g. a Discord channel.

Payload

• the exception/error
• the extension/core and probably the area (file/class/component/data provider/...) the exception was originating from
• the registered name, else any other identification (e.g. computer name) - if choosing to send to Discord it could be helpful to be able to optionally supply a Discord user name in the Platform/Paratext registration dialog

Steps

• [ ] choose a tool that listens for exceptions and errors or tails the logs
• [ ] add a setting "Report issues to the Paratext team" that controls sending this (enabled by default, only available when global internet access is turned on)
• [ ] provide a way for devs & testers to decide after the fact if they want to send it or not (they might be changing code and expect exceptions OR they might be testing a version without modification and want to record and send it)
• [ ] decide on the place where those exceptions would arrive and can be replied to (e.g. a Discord channel)

[irahopkinson]

There are a lot of existing tools for this. Some examples in use in SIL:

• Keyman uses Sentry - its a pay-for service but Keyman has a free license
• Scripture Forge uses BugSnag - used on the open tier