search

metakgp / mftp

CDC noticeboard scraper
GNU Affero General Public License v3.0
34 stars 42 forks source link

[IMPROVEMENT] Failure Monitoring #40

Closed thealphadollar closed 1 year ago

thealphadollar commented 3 years ago

Context

If and when #38 is implemented using Heroku Scheduler, we will need a better way to get notified when the service is not working. Here are key things to note:

  1. When we are running on the Heroku scheduler, there is a "very rare" chance of the job not running or getting missed.
  2. The above is taken care of by Heroku itself, and we do not have to worry about the same. So, the fault we should be notified of is when the script runs but fails.

Requirement

A localized (can pinpoint the exact place that threw the error) and minimal (so that the maintainers do not mark it as spam and multiple maintainers can be added). A good way would be to use the existing mailing mechanism setup using Mailgun REST API. We should also aim at keeping the configuration and reconfiguration overhead as low as possible, if feasible, we should pass it from Github itself.

NOTE: this should ideally be done after #38

Resources

thealphadollar commented 3 years ago

cc/ @iakshat @icyflame What ideas do you have regarding the above?

nilesh05apr commented 1 year ago

@thealphadollar is there a way to monitor failure for github actions?

thealphadollar commented 1 year ago

Yes. As we implement it, it'll show us in the actions tab if it fails or succeeds.

proffapt commented 1 year ago

Closing this since, it won't be possible to host this on heroku anymore because of the discontinuation of free plan on heroku. And the workflow will be different and also already considered int the revamp todo list: https://github.com/metakgp/mftp/issues/55