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
Add logging to the /subscribersPOST endpoint that logs failed subscriber creation to Sentry
Configure ZAP Search back end to integrate with Sentry for error logging
Use the existing zap-search-server app in Sentry
Use job id returned by contact creation endpoint to poll Import Contacts Status endpoint until the job returns a completed, or errored, or failed status.
If any unsuccessful status is reported, or if maximum polling time limit is reached, log details to Sentry with user's email, anonymous_id uuid, and selected subscription topics
Existing /subscribers endpoint should still return when the original contact creation endpoint returns successfully.
The text was updated successfully, but these errors were encountered:
@dhochbaum-dcp I don't have an exact polling rate and max time limit in mind but in general it can be longer with longer pauses between attempts - something like 5 minutes, checking every 10-30 seconds.
@dhochbaum-dcp - @horatiorosa did a spike looking at different Sentry packages for Nest a while back because, at the time, Sentry didn't have an official one. However, they came out with one recently so I say let's try using that :D
Add logging to the
/subscribers
POST
endpoint that logs failed subscriber creation to Sentryzap-search-server
app in Sentrycompleted
, orerrored
, orfailed
status./subscribers
endpoint should still return when the original contact creation endpoint returns successfully.The text was updated successfully, but these errors were encountered: