As a member of the Engagement team,
I want a SOP that details how to monitor ReportStream Items that did not pass a particular step in the pipeline,
so that I can ensure the system is running properly and is not misconfigured.
Description/Use Case
Engagement team is asking an "Internal Message Monitoring SOP." However, before creating such a document, the Universal Pipeline needs to be evaluated to see if it is logging all "errors" and "failures" and if its doing it in the best/cleanest/easiest to use manner. The purpose of this ticket is to create an SRD that details implementation details for "Internal Message Monitoring" that meets criteria expressed in the product brief.
Risks/Impacts/Considerations
Dev Notes
Acceptance Criteria
[ ] SRD created that details an Internal Message Monitoring Support feature
User Story
As a member of the Engagement team, I want a SOP that details how to monitor ReportStream Items that did not pass a particular step in the pipeline, so that I can ensure the system is running properly and is not misconfigured.
Description/Use Case
Engagement team is asking an "Internal Message Monitoring SOP." However, before creating such a document, the Universal Pipeline needs to be evaluated to see if it is logging all "errors" and "failures" and if its doing it in the best/cleanest/easiest to use manner. The purpose of this ticket is to create an SRD that details implementation details for "Internal Message Monitoring" that meets criteria expressed in the product brief.
Risks/Impacts/Considerations
Dev Notes
Acceptance Criteria