Maintenance: Onboarding On Call Duty

[davidcalabrese0324]

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
  • [ ] Document in the ticket why messages got thrown in the poison queue and resolution
  • [ ] Create follow up ticket for resolution if necessary
• [ ] Primary point-of-contact for any Engagement Support problems that occur during the sprint (including status of those issues)
  • [ ] Attach any support tickets that were worked on during the sprint to this ticket
• [ ] 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
  • [ ] Update ticket if there are any missing codes
• [ ] Monitor Azure dashboard for any dropped messages by going to the dashboard in azure here: https://portal.azure.com/#@cdc.onmicrosoft.com/dashboard/arm/subscriptions/7d1e3999-6577-4cd5-b296-f518e5c8e677/resourcegroups/prime-data-hub-test/providers/microsoft.portal/dashboards/9a35cfea-cebd-4c9e-9a63-32c5d510d528
  • [ ] Update ticket with any findings
• [ ] LIVD table updates