CDCgov
Update Azure Logging to Include Mapping Failures
User Story
As an Engagement Engineer, I need to know when there is a Mapping Failure – so that I can help resolve the failures in a timely manner.
Description/Use Case
Engagement team has created a UP Monitoring Dashboard in the Azure logging environment. However, these warnings are not discoverable in the Azure logging environment. Therefore, we want to add these warnings to be monitored in the existing Monitoring Dashboard and include a Slack integration that will proactively inform the Engagement team to ensure that no messages are dropped due to this issue.
Azure Logging Requirements:
All "Mapping Failures" currently returned by the existing Metabase query, trigger an event in Azure that can be queried in the Azure Logging interface and shown on the UP Monitoring Dashboard The "Mapping Failure" item event is a unique event The "Mapping Failure" item event includes All standard item events: submittedReportIds [] submittedItemIndex parentReportId parentItemIndex childReportId childItemIndex sender blobUrl pipelineStepName topic trackingId timestamp queueMessage BundleDigestLabResult New Azure Event is documented where needed, including but not limited to Azure Event Proposal LucidChart
Risks/Impacts/Considerations
Use this section to briefly list out any risks/impacts that may come about, as a result of the proposed solution.
- [System performance may be slowed]
- [Only a single search parameter can be used]
Dev Notes
Use this section to describe any useful technical information to duplicate an issue or explain requirements related to this ticket without providing implementation details.
- [Provided is the data that was used to replicate the issue...]
- [To test, use SimpleReport upload CSV page to ...]
Acceptance Criteria
- [] Gain alignment with Chris Kuryak and Victor Chaparro of format of new/ updated events.
- [] Azure event created that enables us to know when an item fails to map to a receiver
- [] Lucid Chart updated if necessary.
Deprioritized. @wcutshall working with @the-andrew now on KT for shadow migrations.
@wcutshall started this one, @jack-h-wang going to pick up and continue. Will need to go back to @wcutshall if drawdown happens before it gets completed.
