To update, here are peak daily values values: route postaccountuiddevicedeviceidupdate

Tue 01/31  839
Wed 02/01  902
Thu 02/02 1065
Fri 02/03  960
Sat 02/04  898
Sun 02/05  859
Mon 02/06 1115
Tue 02/07 1648
Wed 02/08 1258
Thu 02/09 1079

So, appears to be abating.

For access to Kibana, contact Wesley Dawson [email protected]

On 02/08/17 11:12, Ryan Kelly wrote:
On 9/2/17 05:04, Grisha Kruglov wrote:
Date/time matches the 100% rollout of 51 fennec on Play Store.

Device registration version was bumped in 51 from 1 to 2 in
https://bugzilla.mozilla.org/show_bug.cgi?id=1298727 to "to force
devices to re-register themselves (and send the Push callback url to FxA)".
See https://bugzilla.mozilla.org/show_bug.cgi?id=1298727

Most likely this is what you're seeing, devices re-registering
themselves during a sync.
Great, thanks Grisha!  Sounds like we should expect this traffic to
subside once the installed device population finishes the update.



   Cheers,

     Ryan



On Tue, Feb 7, 2017 at 8:16 PM, Nicholas Alexander
<[email protected] <mailto:[email protected]>> wrote:

     +grisha,

     I think Grisha is most likely to know if things have changed here.

     Nick

     ---------- Forwarded message ----------
     From: *Ryan Kelly* <[email protected] <mailto:[email protected]>>
     Date: Tue, Feb 7, 2017 at 8:13 PM
     Subject: device registration traffic (was re: meeting summary:
     backend chat, 2017-02-07)
     To: dev-fxacct <[email protected]
     <mailto:[email protected]>>, Stefan Arentz <[email protected]
     <mailto:[email protected]>>



     On 8/2/17 14:03, Ryan Kelly wrote:
     >
     > Earlier today we had our weekly backed-focussed catchup and we talked
     > about the following:
     > [...]
     > * The last couple of days have seen a marked uptick in db requests to
     >   update an existing device record.  We need to attempt a bit of user-
     >   agent analysis to see whether this is an early warning of changing
     >   traffic patterns in client code.

     It looks like this uptick in device registration traffic is due to
     Android.  See this kibana graph:


     
https://kibana-fxa-us-west-2.prod.mozaws.net/index.html#dashboard/temp/AVob5ra0TlXM2FwOCRjp
     
<https://kibana-fxa-us-west-2.prod.mozaws.net/index.html#dashboard/temp/AVob5ra0TlXM2FwOCRjp>

     Or the attached carefully-redacted screenshot.

     Stefan, was there a new Firefox for Android release recently that might
     have included changes to FxA device registration?


       Cheers,

         Ryan

     _______________________________________________
     Dev-fxacct mailing list
     [email protected] <mailto:[email protected]>
     https://mail.mozilla.org/listinfo/dev-fxacct
     <https://mail.mozilla.org/listinfo/dev-fxacct>



_______________________________________________
Dev-fxacct mailing list
[email protected]
https://mail.mozilla.org/listinfo/dev-fxacct


_______________________________________________
Dev-fxacct mailing list
[email protected]
https://mail.mozilla.org/listinfo/dev-fxacct

Reply via email to