Error Tracking allows GitLab to receive and act on application errors.

This would be an alternative to Sentry. As you can see on their site there is a lot of functionality that can go into this. But a minimum viable change would be:

1. Create another service desk, but call it Error Tracking.
2. When active it generates an email address: incoming+gitlab-org/gitlab-ce+errors@gitlab.com
   
3. Emails that come in create an issue

Next step would be that similar errors are aggregated. But that doesn't need to be part of the initial product.

BTW Interesting to see that Sentry is integrating source code https://blog.sentry.io/2017/05/01/release-commits.html So it makes sense to combine source code and errors in the same application.

BTW2 If we start working with the AppSignal agent we can make collecting errors automatic instead of people having to configure it https://github.com/smartinez87/exception_notification#rails