Bugzilla

I put this small dashboard together https://sql.telemetry.mozilla.org/dashboard/new-fxa-sync-probe-location to show what values are being returned for the new locations of fxa and sync configured within the telemetry environement (firefox 71 beta only).

Thom, would you mind taking look at that and (dis)confirm the following

1. if  `environment.services.(fxa|sync)_configured` is null (e.g. not set by the client) can we generally assume that the client does not have fxa or sync setup? do you know of any cases where a client might not set the probe to `true` but might actually have one or the other features turned on?

2. related,  will a client only explicitly set the sync probe to false in the case where they have an account configured but sync turned off (in other words, if both fxa and sync are turned off then the value of `environment.services.sync_configured` will be null, but if a client has an account turned on but sync turned off then `environment.services.sync_configured` will be false)?

3. related, the proportion of clients with `environment.services.sync_configured`= false` where `environment.services.fxa_configured = true` seems lower than I expected, though not so low as to be inconceivable. Are there any edge cases, e.g. where maybe the client has the browser open for less than the time it takes to setup sync, where a client should have the sync probe set to `true` but it might get reported as `false`?

lmk if that is hard to parse.

I put this small dashboard together https://sql.telemetry.mozilla.org/dashboard/new-fxa-sync-probe-location to show what values are being returned for the new locations of fxa and sync configured within the telemetry environement (firefox 71 beta only).

Thom, would you mind taking look at that and (dis)confirm the following

1. if  `environment.services.(fxa|sync)_configured` is null (e.g. not set by the client) can we generally assume that the client does not have fxa or sync setup? do you know of any cases where a client might not set the probe to `true` but might actually have one or the other turned on?

2. related,  will a client only explicitly set the sync probe to false in the case where they have an account configured but sync turned off (in other words, if both fxa and sync are turned off then the value of `environment.services.sync_configured` will be null, but if a client has an account turned on but sync turned off then value will be false)?

3. related, the proportion of clients with `environment.services.sync_configured= false` where `environment.services.fxa_configured = true` seems lower than I expected, though not so low as to be inconceivable. Are there any edge cases, e.g. where maybe the client has the browser open for less than the time it takes to setup sync, where a client should have the sync probe set to `true` but it might get reported as `false`?

lmk if that is hard to parse.