As a developer,
I want to know in a timely fashion if an error encountered in the fundraising frontend,
so that I can remove the cause of that error.
Acceptance Criteria:
Background:
At the moment, the errors are logged, but nobody looks at the log file. Somehow, the developers should be notified, but recurring errors should not produce a flood of notifications. Something like https://airbrake.io/ would be nice.
Look like https://sentry.io/ (which is open source and can be installed as a local service) has exactly what we need - rollup of events, notifications, analytics.
I only know sentry as pay-for SAAS (a good one at that).
Maybe we should look at the actual requirements (e.g. "not self-hosted"(?)) and then at actual implementations, otherwise we derive our requirements from the marketing pamphlet of the top dogs, instead of our real need.
Collecting some thoughts here for the next story time:
I'd like errors in the log to behave like a ticket:
To estimate the severity of the error, it would also be helpful if we had some kind of indication how many times the error occurred so far/since it was closed.
Zabbix (the monitoring system our hoster uses) is capable of log file monitoring to some extent:
https://www.zabbix.com/documentation/3.4/manual/config/items/itemtypes/log_items
This does not look as sophisticated as the above mentioned products, but the maintenance wouldn't be our responsibility.