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

Bender uptime #437

Closed
2 tasks
jakemorr opened this issue Aug 19, 2020 · 3 comments
Closed
2 tasks

Bender uptime #437

jakemorr opened this issue Aug 19, 2020 · 3 comments
Assignees
Labels
Ready User Story or Task Ready to be pulled into sprint Task Technical task that cannot be written as a user story

Comments

@jakemorr
Copy link
Contributor

jakemorr commented Aug 19, 2020

Describe the task
Be notified if bender (bot that collects forecasts) doesn't run successfully.

Acceptance Criteria

  • If cronjob exists with errors, a notification must be sent.
  • Notification must be sent to the same users as configured in uptime robot.

Additional context

  • The idir password for bender changed, and we didn't notice that it was failing to run for 4 days.
@jakemorr jakemorr added Critical Task Technical task that cannot be written as a user story Ready User Story or Task Ready to be pulled into sprint labels Aug 19, 2020
@Sybrand
Copy link
Contributor

Sybrand commented Sep 2, 2020

Does this include Marvin uptime?

@jakemorr
Copy link
Contributor Author

jakemorr commented Sep 2, 2020

@Sybrand it could or we could split it out, it depends how much effort it is to do together vs to split it up. does adding Marvin add complexity?

@Sybrand
Copy link
Contributor

Sybrand commented Sep 2, 2020

@Sybrand it could or we could split it out, it depends how much effort it is to do together vs to split it up. does adding Marvin add complexity?

I'm guessing that figuring out how to do it for one is 99% of the effort - so doing them both at once makes sense to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Ready User Story or Task Ready to be pulled into sprint Task Technical task that cannot be written as a user story
Projects
None yet
Development

No branches or pull requests

3 participants