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.

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

Understand ReportStream Incident Classification #1577

Open
1 task
JohnNKing opened this issue Nov 11, 2024 · 1 comment
Open
1 task

Understand ReportStream Incident Classification #1577

JohnNKing opened this issue Nov 11, 2024 · 1 comment
Assignees
Labels

Comments

@JohnNKing
Copy link
Contributor

JohnNKing commented Nov 11, 2024

Backlog Task

Understand how ReportStream classifies production support issues, incidents, etc., so we can decide how/if we want to align with them and so we can communicate effectively with them.

Completion Criteria

  • Our incident process has been updated to better align with how ReportStream classifies production incidents or issues.

Tasks

  • [ ]

Other Notes

  • Any other notes to help clarify this task for the team
@JohnNKing JohnNKing added the foundational A foundational backlog task label Nov 11, 2024
@JohnNKing JohnNKing removed the foundational A foundational backlog task label Nov 12, 2024
@jbiskie
Copy link
Contributor

jbiskie commented Nov 12, 2024

Notes from chat with @brick-green and @GilmoreA6:

  • I only remember an incident being declared in the event that PHI was leaked otherwise everything was considered a production support issue
  • The only other times we declared incidents were when RS was down entirely and unable to process any messages

@csweet92 csweet92 self-assigned this Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants