openedx / openedx/axim-engineering
Setup Uptime Monitoring for https://openedx.org
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
We own https://openedx.org but we have no monitoring to tell us whether it's up or down. We should setup something so that we can find this out fairly quickly rather than be told by consumers of the website.
Per earlier discussion, this doesn't mean we need a strong SLA or a paging setup. For the initial version of this, notifying via e-mail or slack or both is probably sufficient.
AC:
- https://openedx.org is being monitored for outages.
- https://openedx.org is being monitored for valid SSL certs.
- Notifications go to e-mail(tcril-engineering@tcril.org) or Slack(#tcril-engineering) or both.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the uptime target, https://openedx.org, and the acceptance criteria. Determine how outage and valid SSL-certificate checks can notify tcril-engineering@tcril.org, #tcril-engineering, or both without introducing paging or a strong SLA. Done means the site is monitored for both conditions and the selected notification path is verified.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100