1837517 - Add Nimbus Instrumentation for Printing for the Print from Menu Option in Android

Status: RESOLVED FIXED

(Fenix :: Experimentation and Telemetry, enhancement, P1)

Description

[Olivia Hall [:olivia]]

The new Print UI for printing from the menu for Fenix will need Nimbus experimentation setup to control showing/hiding the option.

Comment 1

[Olivia Hall [:olivia]]

Telemetry should also be added at this point of :

• print_tapped - source: [pdf, non-pdf], menu: [share, base] (may need separate pings of print_tapped_share and print_tapped_base, depending on implementation)
  Edit: Instead of print_tapped for the base menu, expand telemetry of browser_menu_action to include print_content
• print_completed
• print_failure - reason - [browsing_context, no_print_settings, etc.]

Comment 2

[Olivia Hall [:olivia]]

Attachment: Data Review Request for Printing from Menu Feature

Comment 3

[Roger Yang [:royang]]

Comment on attachment 9341109 [details]
Data Review Request for Printing from Menu Feature

DATA COLLECTION REVIEW RESPONSE:

1. Is there or will there be documentation that describes the schema for the ultimate data set in a public, complete, and accurate way?

Yes, through the metrics.yaml file and the Glean Dictionary.

2. 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.

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

N/A, collection to be removed or renewed by version 122

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

Category 1 and 2, Technical and Interaction data

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

Default on for all channels.

6. Does the instrumentation include the addition of any new identifiers?

No

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

Yes

8. Does the data collection use a third-party collection tool?

No

Result: data-review+

Comment 4

[Olivia Hall [:olivia]]

Attachment: Additional Data Request

During implementation, realized probe print_tapped for both menu and share is indeed needed to ensure that the extra is captured for both.

Additional data review is for adjustment on new probe print_tapped to cover both cases and new probe for share sheet of share_menu_action with item extra of print.

Comment 5

[Roger Yang [:royang]]

Comment on attachment 9343115 [details]
Additional Data Request

DATA COLLECTION REVIEW RESPONSE:

1. Is there or will there be documentation that describes the schema for the ultimate data set in a public, complete, and accurate way?

Yes, through the metrics.yaml file and the Glean Dictionary.

2. 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.

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

N/A, collection to be removed or renewed by version 122

4. 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 data

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

Default on for all channels.

6. Does the instrumentation include the addition of any new identifiers?

No

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

Yes

8. Does the data collection use a third-party collection tool?

No

Result: data-review+

Comment 6

[BMO Github Automation]

Attachment: [mozilla-mobile/firefox-android] Bug 1837517 - Additional Print Telmetry and Nimbus setup (#2798)

Comment 7

[BMO Github Automation]

Authored by https://github.com/ohall-m
https://github.com/mozilla-mobile/firefox-android/commit/7c2055b459ab6d609c9bf14c2c69f9eab1b53090
[main] Bug 1837517 - Additional Print Telmetry and Nimbus setup