## Scope The queries are limited to the pings received between Feb. 2 and 8, 2020. This includes 142,466 pings from 33,844 clients. ## Ping and Client Counts ### Aggregate With approximately 8k DAU we're seeing around 20k pings per day. ([query](https://sql.telemetry.mozilla.org/queries/68194/source)) Per-client: https://sql.telemetry.mozilla.org/queries/68126/source#172232 This looks like a nice curve and is what I would expect to see as most users are sending less than 10 pings per day and we see some "heavy" users sending as many as 75 pings per day (a cohort of 17 users at this level) ## Sequence Numbers ### Holes and Dupes https://sql.telemetry.mozilla.org/queries/68141/source#172261 105 clients (0.31%) have any holes/dupes in their sequence record, this is low and that is good, but it might bear a little more investigation to see if there is room for improvement. On the whole, it appears that dupes are slightly more prevalent than holes but these seem to be evenly distributed among the sequence numbers of clients so I don't think there is any correlation to new or old clients with regards to either dupes or holes. ## Field Compositions durations: https://sql.telemetry.mozilla.org/queries/68163/source#172373 I struggled to get a histogram out of BigQuery on this one, my lack of knowledge being the limiting factor. Other than that, we see a nice logarithmic curve of client durations which looks like what I would expect. client_info stuff and locale: https://sql.telemetry.mozilla.org/queries/68197/source There are a few null durations (64 out of 142k) and a few zero durations (2345 out of 142k) that we might want to investigate, but overall the rates are low, which is good. The rest of the fields look to be as expected. ## Delay https://sql.telemetry.mozilla.org/queries/68127/source#172233 This is measured using the header date and the submission_timestamp, we see the vast majority of clients' pings arrive < 1 minute, but we do have a few (4364) that arrived between 1-2 minutes, and then a smattering of time travellers. Longer than 3 hours is a cohort of only 66 out of the 142k pings, which seems pretty good. All in all, I think we may want to investigate a little more about why there are more time-travellers than I would have expected, but I suspect it has more to do with timezones or other oddities rather than anything buggy. We see only 0.04% of over-3-hour submission delays which is fantastic. Pings are getting to us in a reasonable time. 1.5% are received before they're recorded. 95% of pings are received within a minute of their recording. I struggled with a good visualization for this data but would be happy to entertain suggestions. ## Conclusion I conclude that Lockwise-Android baseline pings look good with the exception of a few more time-travellers than I would have expected, and a similar hole/dupe problem as seen on other apps.
Bug 1596168 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
## Scope The queries are limited to the pings received between Feb. 2 and 8, 2020. This includes 142,466 pings from 33,844 clients. ## Ping and Client Counts ### Aggregate With approximately 8k DAU we're seeing around 20k pings per day. ([query](https://sql.telemetry.mozilla.org/queries/68194/source)) Per-client: https://sql.telemetry.mozilla.org/queries/68126/source#172232 This looks like a nice curve and is what I would expect to see as most users are sending less than 10 pings over the sample period and we see some "heavy" users sending as many as 75 pings over the sample period (a cohort of 17 users at this level) ## Sequence Numbers ### Holes and Dupes https://sql.telemetry.mozilla.org/queries/68141/source#172261 105 clients (0.31%) have any holes/dupes in their sequence record, this is low and that is good, but it might bear a little more investigation to see if there is room for improvement. On the whole, it appears that dupes are slightly more prevalent than holes but these seem to be evenly distributed among the sequence numbers of clients so I don't think there is any correlation to new or old clients with regards to either dupes or holes. ## Field Compositions durations: https://sql.telemetry.mozilla.org/queries/68163/source#172373 I struggled to get a histogram out of BigQuery on this one, my lack of knowledge being the limiting factor. Other than that, we see a nice logarithmic curve of client durations which looks like what I would expect. client_info stuff and locale: https://sql.telemetry.mozilla.org/queries/68197/source There are a few null durations (64 out of 142k) and a few zero durations (2345 out of 142k) that we might want to investigate, but overall the rates are low, which is good. The rest of the fields look to be as expected. ## Delay https://sql.telemetry.mozilla.org/queries/68127/source#172233 This is measured using the header date and the submission_timestamp, we see the vast majority of clients' pings arrive < 1 minute, but we do have a few (4364) that arrived between 1-2 minutes, and then a smattering of time travellers. Longer than 3 hours is a cohort of only 66 out of the 142k pings, which seems pretty good. All in all, I think we may want to investigate a little more about why there are more time-travellers than I would have expected, but I suspect it has more to do with timezones or other oddities rather than anything buggy. We see only 0.04% of over-3-hour submission delays which is fantastic. Pings are getting to us in a reasonable time. 1.5% are received before they're recorded. 95% of pings are received within a minute of their recording. I struggled with a good visualization for this data but would be happy to entertain suggestions. ## Conclusion I conclude that Lockwise-Android baseline pings look good with the exception of a few more time-travellers than I would have expected, and a similar hole/dupe problem as seen on other apps.
## Scope The queries are limited to the pings received between Feb. 2 and 8, 2020. This includes 142,466 pings from 33,844 clients. ## Ping and Client Counts ### Aggregate With approximately 8k DAU we're seeing around 20k pings per day. ([query](https://sql.telemetry.mozilla.org/queries/68194/source)) Per-client: https://sql.telemetry.mozilla.org/queries/68126/source#172232 This looks like a nice curve and is what I would expect to see as most users are sending less than 10 pings over the sample period and we see some "heavy" users sending as many as 75 pings over the sample period (a cohort of 17 users at this level) ## Sequence Numbers ### Holes and Dupes https://sql.telemetry.mozilla.org/queries/68141/source#172261 105 clients (0.31%) have any holes/dupes in their sequence record, this is low and that is good, but it might bear a little more investigation to see if there is room for improvement. On the whole, it appears that dupes are slightly more prevalent than holes but these seem to be evenly distributed among the sequence numbers of clients so I don't think there is any correlation to new or old clients with regards to either dupes or holes. ## Field Compositions durations: https://sql.telemetry.mozilla.org/queries/68163/source#172373 I struggled to get a histogram out of BigQuery on this one, my lack of knowledge being the limiting factor. Other than that, we see a nice logarithmic curve of baseline ping durations which looks like what I would expect. client_info stuff and locale: https://sql.telemetry.mozilla.org/queries/68197/source There are a few null durations (64 out of 142k) and a few zero durations (2345 out of 142k) that we might want to investigate, but overall the rates are low, which is good. The rest of the fields look to be as expected. ## Delay https://sql.telemetry.mozilla.org/queries/68127/source#172233 This is measured using the header date and the submission_timestamp, we see the vast majority of clients' pings arrive < 1 minute, but we do have a few (4364) that arrived between 1-2 minutes, and then a smattering of time travellers. Longer than 3 hours is a cohort of only 66 out of the 142k pings, which seems pretty good. All in all, I think we may want to investigate a little more about why there are more time-travellers than I would have expected, but I suspect it has more to do with timezones or other oddities rather than anything buggy. We see only 0.04% of over-3-hour submission delays which is fantastic. Pings are getting to us in a reasonable time. 1.5% are received before they're recorded. 95% of pings are received within a minute of their recording. I struggled with a good visualization for this data but would be happy to entertain suggestions. ## Conclusion I conclude that Lockwise-Android baseline pings look good with the exception of a few more time-travellers than I would have expected, and a similar hole/dupe problem as seen on other apps.