Ticket #1285 (assigned enhancement)
Errors cause emails
Reported by: | dread | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | ckan-future |
Component: | ckan | Keywords: | |
Cc: | Repository: | ckan | |
Theme: | none |
Description
Currently a sysadmin gets an email when an exception is not caught. But there are occasions when we DO want to catch an exception so we can fail nicely for the user, but the sysadmin STILL gets an email to know to fix something. e.g. if there is an exception when search indexes a package. You want to catch the exception and still run any other notify calls.
Change History
comment:2 Changed 2 years ago by thejimmyg
- Owner set to thejimmyg
- Status changed from new to assigned
I could write some middleware to handle this. Can we come up with a list of exceptions not to catch or should I create a base exception called "NoEmailReportTriggeredException?()" which exceptions for this purpose have to be derived from or which code has to raise?
Note: See
TracTickets for help on using
tickets.
Another instance is when the database tables are not created and you want to both display a sensible error and have an email alert. #1290