Verify PagerDuty onboarding with individual test pages
- Dominant language
- Python
- Stars
- 1
- Forks
- 2
- Avg merge
- 12h 9m
- Merged PRs (30d)
- 10
Description
## Done Criteria
1. Everyone expected to be page-able for FOC is listed in the PagerDuty onboarding tracker and included in the `Filecoin Onchain Cloud` PagerDuty group.
2. Each person receives an individual PagerDuty test page and confirms they can acknowledge it through their intended notification path.
3. Any failed/missed pages are remediated, or a clear follow-up owner/action is recorded before this ticket is closed.
## Why Important
Being added to PagerDuty is not enough; we need evidence that each responder has their profile/app/notification settings configured correctly before we rely on paging for sev2.x events.
This is especially important because GitHub issue #20 gets us to “people are added,” but PagerDuty does not make it easy to see whether everyone has actually completed setup on their side.
## Notes
Follow-up to https://github.com/FilOzone/tpm-utils/issues/20, specifically:
https://github.com/FilOzone/tpm-utils/issues/20#issuecomment-4533118509
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.