Track errors with Sentry
It appears that currently the easiest way to look for errors is looking at the webhook hisotry. I saw the error from there and fixed it 2~3 days after the error was introduced: !10 (merged)
We might want to have sentry or something like that if we can. From there we can make notifications.
So far it's not too severe because we don't have much functionalities there, but as we grow and with the new feature #22 (closed) this will be getting more and more important, especially when this service is reactive and if something was lost during the period, they were probably lost forever unlike that we can restore the mistakes in triage-ops
This might be much more important than having a good way to test it. At least now we can test it via skipping when it's event.from_gitlab_org?
and try it in triage-test (this is a testing project which has project webhook set against triage-serverless, so we can try everything from production for that project without affecting gitlab-org
group when we did check event.from_gitlab_org?
as a feature flag)