1801019 - Ensure its possible to differentiate the extension vs. the component implementation in telemetry

Status: VERIFIED FIXED

(Firefox :: Screenshots, task)

Description

[Sam Foster [:sfoster] (he/him)]

Once we enable the component implementation (bug 1789727) we need to be able to clearly differentiate its users from those using the extension, so we can keep an eye on any drop or change in use patterns.

Comment 2

[Niklas Baumgardner [:niklas]]

Attachment: Bug 1801019 - Add telemetry for screenshots component. r=sfoster

Comment 3

[Niklas Baumgardner [:niklas]]

Attachment: Data review request.md

Comment 4

[Chris H-C :chutten]

Comment on attachment 9313827 [details]
Data review request.md

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.

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

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

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

Yes, Sam Foster is responsible.

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

Category 2, Interaction.

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 the data collection use a third-party collection tool?

No.

---

Result: datareview+

Comment 5

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/aaf82d1483ad
Add telemetry for screenshots component. r=sfoster

Comment 6

[Atila Butkovits]

Backed out for causing failures at browser_screenshots_telemetry_tests.js

Backout link: https://hg.mozilla.org/integration/autoland/rev/d89ff3aa16690e897454e27d1bf09c3731e95823

Push with failures: https://treeherder.mozilla.org/jobs?repo=autoland&selectedTaskRun=bQJOh5xxRQ2dYFfPmVJfCg.0&resultStatus=testfailed%2Cbusted%2Cexception%2Cretry%2Cusercancel&revision=aaf82d1483adc6d6d2eeb5af8702324f169c02b4

Failure log: https://treeherder.mozilla.org/logviewer?job_id=406425536&repo=autoland&lineNumber=9279

Comment 7

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/d853ddfd853e
Add telemetry for screenshots component. r=sfoster

Comment 8

[Marian-Vasile Laza]

Backed out changeset d853ddfd853e (Bug 1801019) for bc failures on browser_screenshots_telemetry_tests.js.
Backout link
Push with failures <--> bc2
Failure Log

Comment 9

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/4646d9d5fb82
Add telemetry for screenshots component. r=sfoster

Comment 10

[Marian-Vasile Laza]

https://hg.mozilla.org/mozilla-central/rev/4646d9d5fb82

Comment 11

[Negritas Sergiu, Desktop QA]

Hello! I can confirm that the issue is fixed with firefox 123.0a1 (2024-21-01) on Windows 10, Ubuntu 22.04 and MacOS 12.6. I will update the flags and and set the status of this issue.

Have a nice day!