You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 5, 2018. It is now read-only.
On certain responses such as errors (http status 500), it would be valuable to generate an alert such as an email or sms in order to notify someone about this.
This could be handled on a per-channel basis using alert groups (defaultchannel-mapping.json):
We could initially then allow for email and clickatell SMS's (since we already have experience with them and have an account we can use). Setup could be in a config file such as resources/alertGroups.json:
In the above examples, if a transaction responds with anything in the 4xx range, emails and SMSs will be sent out to adminGroup1, while if a transaction responds with 500, an SMS will be sent out to adminGroup2.
In order not to spam people, we could restrict it to one alert per 24hour period (or handle this per config).
The text was updated successfully, but these errors were encountered:
After losing a lot of time struggling to get this functionality to (unsuccessfully) work in Mule, I decided to switch and set this up as a set of cron triggered python scripts: https://github.com/jembi/openhim-report-tasks
Python ftw :)
Closing this issue for now, we can reopen it if someone feels like implementing this natively in the Mule HIM.
On certain responses such as errors (http status 500), it would be valuable to generate an alert such as an email or sms in order to notify someone about this.
This could be handled on a per-channel basis using alert groups (
defaultchannel-mapping.json
):We could initially then allow for email and clickatell SMS's (since we already have experience with them and have an account we can use). Setup could be in a config file such as
resources/alertGroups.json
:In the above examples, if a transaction responds with anything in the 4xx range, emails and SMSs will be sent out to adminGroup1, while if a transaction responds with 500, an SMS will be sent out to adminGroup2.
In order not to spam people, we could restrict it to one alert per 24hour period (or handle this per config).
The text was updated successfully, but these errors were encountered: