Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[IMPROVEMENT] Failure Monitoring #40

Closed
thealphadollar opened this issue Nov 12, 2020 · 4 comments
Closed

[IMPROVEMENT] Failure Monitoring #40

thealphadollar opened this issue Nov 12, 2020 · 4 comments

Comments

@thealphadollar
Copy link
Contributor

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
Copy link
Contributor Author

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

@nilesh05apr
Copy link

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

@thealphadollar
Copy link
Contributor Author

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

@proffapt
Copy link
Member

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: #55

@proffapt proffapt closed this as not planned Won't fix, can't repro, duplicate, stale Aug 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants