You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we have sent a request to a provider, log the time from created until we have an initial response from the provider (Twilio, Pinpoint, SES, etc.). This is applicable to SMS and email requests.
Ticket is understood, and QA has been contacted (if the ticket has a QA label).
User Story(ies)
As VA Notify I want to track how long it takes from request received until we have sent it to a provider So that we can start to understand more fine-grained performance
Additional Info and Resources
Be careful if log_notification_total_time is reused. Loosening the guard statement has risks for improper reporting. It may be best to just make a new method, only called for pre-provider total time logging.
Acceptance Criteria
Create a timestamp when the request first enters the post_notifications method
Pass that along to the created/persisted notification so the created_at can be set with it
Just prior to calling the provider, log the total time
This work is added to the sprint review slide deck (key win bullet point and demo slide)
QA Considerations
Just a logging thing. Shouldn't need more than a validation it is logging for each use case (Twilio, Pinpoint, SES).
Potential Dependencies
The text was updated successfully, but these errors were encountered:
User Story - Business Need
When we have sent a request to a provider, log the time from created until we have an initial response from the provider (Twilio, Pinpoint, SES, etc.). This is applicable to SMS and email requests.
User Story(ies)
As VA Notify
I want to track how long it takes from request received until we have sent it to a provider
So that we can start to understand more fine-grained performance
Additional Info and Resources
Be careful if
log_notification_total_time
is reused. Loosening the guard statement has risks for improper reporting. It may be best to just make a new method, only called for pre-provider total time logging.Acceptance Criteria
QA Considerations
Just a logging thing. Shouldn't need more than a validation it is logging for each use case (Twilio, Pinpoint, SES).
Potential Dependencies
The text was updated successfully, but these errors were encountered: