Engagement On Call Duty - Sprint 95

[chris-kuryak]

Responsibilities and Acceptance Criteria for this sprint

One engineer per sprint is assigned on-call duty. It is that engineer's responsibility to know the "pulse" of BE issues/health during the sprint. This includes the following responsibilities:

• [ ] Monitor poison queue messages and re-process if needed. Information on how to reprocess messages can be found here: https://github.com/CDCgov/prime-reportstream/blob/master/prime-router/docs/standard-operating-procedures/Poison-queue/poison-queue-management.md
• [ ] Primary point-of-contact for any Engagement Support problems that occur during the sprint (including status of those issues)
• [ ] Resolve pager-duty engagement alerts
• [ ] Resolve all security (high-priority) Transport related Dependabots
• [ ] Monitor missing mappings code-to-condition table. Information on how to check missing mappings can be found here: https://github.com/CDCgov/prime-reportstream/blob/master/prime-router/docs/standard-operating-procedures/update-observation-mapping-table.md
• [ ] Monitor if recently onboarded STLTs to the UP received any messages for new conditions.
• [ ] LIVD table updates