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.

Sign up for GitHub

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

Jump to bottom

Improve logging and notifications for full pipeline #377

Open
6 tasks
ethanwhite opened this issue Feb 1, 2021 · 0 comments
Open
6 tasks

Improve logging and notifications for full pipeline #377

ethanwhite opened this issue Feb 1, 2021 · 0 comments

Comments

@ethanwhite
Copy link
Member

The automated pipeline needs to simultaneously accomplish two things:

  1. Be as robust as possible to errors caused by things like upstream data issues
  2. Make sure that errors are quickly identified so that they can be fixed

Here's my first draft of a checklist for things we need to do in this space.

  • Implement logging for each step of PortalData
  • Implement notifications for failures at any step for PortalData
  • Fail PortalData if result of update would break things downstream
  • Implement logging in portalcasting
  • In portalPredictions implement notifications for failures at any step for portalcasting
  • Fail portalPredictions if result of update would result in errors on website

@gmyenni @juniperlsimonis @henrykironde Am I thinking about this right? Are there other things that need to be on the list?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ethanwhite