opensafely-core / opensafely-core/backend-server
Expose reboot activity in backends
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 1
- Forks
- 5
- Avg merge
- 1h 36m
- Merged PRs (30d)
- 2
Description
When we get alerts for TPP, frequently they are network blips, or can be that the server has rebooted.
The incident response is quite different in those scenarios, so it would good to expose reboot events to help distinguish them.
This probably looks like:
- a run-once-at-boot systemd service that runs something like a
python3 -m jobrunner.cli.notify_rebootcommand - that command pings a special purpose job-server API that post a message to #tech-support-channel saying "backend FOO was rebooted at $TIME".
Possibly we want separate "going down" and "coming up" messages
Contributor guide
No contributing guide indexed for this repository
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
Begin with the proposed entry point python3 -m jobrunner.cli.notify_reboot and the special-purpose job-server API. Establish whether notifications should cover boot only or both down and up events, then define delivery to #tech-support-channel and the message format. The issue names no files or tests, so the implementation scope must be established first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100