These errors are available in the service/frontend-prod log group (see: Error subscribing user: fetch failed).
Steps
Evaluate if current error logging messages are ideal in the subscribe.ts file. Ie it might be better to have them more uniform or start with Sendy error: to make them easier to find in the logs.
Determine number of errors to initiate an alert. I would imagine this is 1 since any errors subscribing someone would require investigation
Determine best strategy for log / filtering and alerts
Anomoly detector or metric and alarm
Create alarm
Questions
Is there a way to test this once it is implemented?
Summary
When there is an error subscribing users to Sendy, we should get an alert.
Errors for subscribing are logged here: https://github.com/HHS/simpler-grants-gov/blob/00ca83fb01d41d317c8fe6d40d9a1a4d2f0d332e/frontend/src/pages/api/subscribe.ts#L63
These errors are available in the
service/frontend-prod
log group (see:Error subscribing user: fetch failed
).Steps
subscribe.ts
file. Ie it might be better to have them more uniform or start withSendy error:
to make them easier to find in the logs.Questions
Acceptance criteria