Closed Bug 1635872 Opened 5 years ago Closed 5 years ago

Add telemetry to measure usage of WebVR, independently of WebXR

Categories

(Core :: WebVR, enhancement)

enhancement

Tracking

()

RESOLVED FIXED
mozilla78
Tracking Status
firefox78 --- fixed

People

(Reporter: kip, Assigned: daoshengmu)

References

Details

Attachments

(2 files)

We wish to add telemetry to help us determine usage of WebVR, which will be deprecated in favor of WebXR. We will use this telemetry to determine how long to leave WebVR enabled, giving developers sufficient time to migrate to WebXR, which will be enabled simultaneously.

Blocks: 1635874

I am going to work on this, I think this is a good practice for me to understand the recent desktop telemetry system.

Assignee: nobody → dmu

I think this is a right place to put our telemetry for identifying if a user uses WebVR or WebXR to enter the immersive mode. From my understanding, only presenting is our defined behavior of using WebVR/XR APIs.

I am trying to avoid some cases like CNN that they just include a JS framework and register VR events, but they do not actually enter the immersive mode.

:chutten, we would like to add a telemetry to help us determine the usage of WebVR and WebXR, and based on the telemetry result to help us determine when we can deprecate WebVR API from Gecko. Please help do the data review. Thanks.

Attachment #9146569 - Flags: data-review?(chutten)
Comment on attachment 9146569 [details] data review request.txt PRELIMINARY NOTES: In the list of proposed measurements please don't forget to name and describe the measurements you're adding. For this instance I assumed "WEBXR_API_MODE" and "Which API was used to enter immersive mode, and how often". If this is incorrect, please provide a more correct and complete list of names and descriptions of your measurements. 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 Telemetry so is documented in its definitions file [Histograms.json](https://hg.mozilla.org/mozilla-central/file/tip/toolkit/components/telemetry/Histograms.json) and the [Probe Dictionary](https://telemetry.mozilla.org/probe-dictionary/). 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, :daoshengmu 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 there need to be a check-in in the future to determine whether to renew the data? No. This collection is permanent. --- Result: datareview+
Attachment #9146569 - Flags: data-review?(chutten) → data-review+

(In reply to Chris H-C :chutten from comment #5)

Comment on attachment 9146569 [details]
data review request.txt

PRELIMINARY NOTES:

In the list of proposed measurements please don't forget to name and
describe the measurements you're adding. For this instance I assumed
"WEBXR_API_MODE" and "Which API was used to enter immersive mode, and how
often". If this is incorrect, please provide a more correct and complete
list of names and descriptions of your measurements.

Sorry for I didn't see and write the proposed measurements description. Like you said, we wanna use "WEBXR_API_MODE" to know how users usee this two APIs and how often.

Pushed by dmu@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/28dbcdf8e6dc Add telemetry to measure usage of WebVR and WebXR. r=kip
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla78
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: