-
Notifications
You must be signed in to change notification settings - Fork 3
Stopped receiving send tab metrics #125
Comments
Looks like this was around the same time we made the changes to move over to the new redshift server, @philbooth any ideas? |
@rfk, I think this was the import job that I couldn't remember anything about when we talked on Vidyo before Christmas. I can't remember what we did then (and can't SSH onto @davismtl, we do have a plan for moving this over to be managed by ops, which is kind-of-in-progress in mozilla/fxa-amplitude-send#79. It should be straightforward to make sure we pick up the missing data when we get that running, so it fills in the blanks. Sorry about it in the meantime though. @jbuck, have you got time tomorrow to chat about getting mozilla/fxa-amplitude-send#79 tested/merged/deployed on |
@philbooth and I talked today about this, and I'll try out the new PR this week |
@philbooth send tab has a huge impact on retention (double it for sync users alone). we're working on a CFR for send tab so this is pretty important. |
Understood @ryanfeeley, please forgive my tardiness! I'm picking it up again right now. |
No worries, I had the numbers memorized as they were so thrilling to me. |
@ryanfeeley my bad, data has been imported into Amplitude now. I haven't got it scripted yet, still need to figure out the best way to do that @philbooth how do you handle 429's for the sync dataset? I'm getting one with: |
I didn't have to so far because of how I was running it before. I'll have a play today and add some backoff logic. |
Ref: #81 |
We can close this now I think. |
See received tabs:
https://analytics.amplitude.com/mozilla-corp/chart/new/voy6ilt
Sent tabs:
https://analytics.amplitude.com/mozilla-corp/chart/new/c8xzmx2
The text was updated successfully, but these errors were encountered: