Skip to content

Verify PagerDuty onboarding with individual test pages #46

@rjan90

Description

@rjan90

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 #20, specifically:
#20 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status
    🐱 Todo

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions