Skip to content
This repository has been archived by the owner on Jul 22, 2024. It is now read-only.

Legacy telemetry data review. #3467

Merged
merged 1 commit into from
Jun 12, 2020
Merged

Legacy telemetry data review. #3467

merged 1 commit into from
Jun 12, 2020

Conversation

daoshengmu
Copy link
Contributor

@daoshengmu daoshengmu commented Jun 4, 2020

Request for data collection review form

All questions are mandatory. You must receive review from a data steward peer on your responses to these questions before shipping new data collection.

  1. What questions will you answer with this data?
  • Adding a UUID uniquely identifying the legacy telemetry client id.
    This is used for supporting legacy telemetry in the deletion-request ping.
  1. Why does Mozilla need to answer these questions? Are there benefits for users? Do we need this information to address product or business requirements?
  • Helping sunset the legacy telemetry.
  1. What alternative methods did you consider to answer these questions? Why were they not sufficient?
  • N/A. this is a new ping
  1. Can current instrumentation answer these questions?
  • N/A, this is a new ping for supporting legacy telemetry in the deletion-request.
  1. List all proposed measurements and indicate the category of data collection for each measurement, using the Firefox data collection categories on the found on the Mozilla wiki.
  • All data is Category 2.
  1. How long will this data be collected?

Until 11/01/2020. Probably, at that time, the legacy telemetry would be no longer exist.

  1. What populations will you measure?
  • All release, beta, and nightly users with telemetry enabled.
  1. Please provide a general description of how you will analyze this data.
  • Glean
  1. Where do you intend to share the results of your analysis?
  • Only on Glean and with Firefox Reality team.

@chutten, please help data review. It seems like I forget to do the data review at #3324

@daoshengmu daoshengmu added this to the #11 polish milestone Jun 4, 2020
@daoshengmu daoshengmu self-assigned this Jun 4, 2020
@chutten
Copy link

chutten commented Jun 11, 2020

The linked PR doesn't appear to be the one that added the uuid.

@daoshengmu daoshengmu force-pushed the legacyTelemetryDataReview branch from 700c91c to 4e8069d Compare June 11, 2020 17:52
@daoshengmu
Copy link
Contributor Author

The linked PR doesn't appear to be the one that added the uuid.

Sorry for my mistake when doing copy-and-paste. The previous metric change is happened at #3384.

@chutten
Copy link

chutten commented Jun 11, 2020

DATA COLLECTION REVIEW RESPONSE:

Is there or will there be documentation that describes the schema for the ultimate data set available publicly, complete and accurate?

Yes. This collection is documented in its metrics documentation.

Is there a control mechanism that allows the user to turn the data collection on and off?

Yes. This collection is Glean so can be controlled through Firefox Reality's Preferences.

If the request is for permanent data collection, is there someone who will monitor the data over time?

No. This collection will expire 2020-11-01.

Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under?

Category 1, Technical.

Is the data collection request for default-on or default-off?

Default on for all channels.

Does the instrumentation include the addition of any new identifiers?

No.

Is the data collection covered by the existing Firefox privacy notice?

Yes.

Does there need to be a check-in in the future to determine whether to renew the data?

Yes. Daosheng Mu is responsible for renewing or removing the collection before it expires on 2020-11-01.


Result: datareview+

@daoshengmu daoshengmu force-pushed the legacyTelemetryDataReview branch from 4e8069d to 8385466 Compare June 11, 2020 20:50
@daoshengmu daoshengmu force-pushed the legacyTelemetryDataReview branch from 8385466 to 9d14e33 Compare June 11, 2020 20:52
@daoshengmu daoshengmu requested a review from keianhzo June 11, 2020 20:53
@keianhzo
Copy link
Contributor

@daoshengmu This can be merged already or we have to wait for some other thing?

@daoshengmu daoshengmu merged commit 66149ff into master Jun 12, 2020
@daoshengmu daoshengmu deleted the legacyTelemetryDataReview branch June 12, 2020 16:59
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants