[Geckoview Streaming Telemetry](https://firefox-source-docs.mozilla.org/toolkit/components/telemetry/obsolete/geckoview-streaming.html) is an obsolete and deprecated module of Legacy Firefox Desktop Telemetry that allowed specific Histograms and Scalars recorded in Gecko to be relayed to geckoview-embedding applications (most notably Firefox for Android) so they could be reported by those embedding applications. It has been obsolete and deprecated since bug 1670261 allowed Gecko and Firefox for Android to share the same Glean. From then on, the best way to get your data to be recorded in Firefox Desktop and Firefox for Android has been to just use Glean. Recently we (Bas and Marc mostly) discovered in bug 1850847 that GVST has likely never worked fully on the release channel due to the Legacy Telemetry API throwing the data away because it was operating in non-unified mode. We need this data to help inform our decisions, so getting this working is of recent and increasing importance. Let's get this working by removing GVST while ensuring the continuity of data reported to Telemetry in Firefox Desktop and to Glean in Firefox for Android. We'll do this by migrating the GVST-using metrics to submit their data more directly: * Move the Fenix-only metrics definitions in `toolkit/components/telemetry/geckoview/streaming/metrics.yaml` to appropriate `metrics.yaml` files in the tree * Record to Glean by using Glean APIs at point of instrumentation of the GVST-using Legacy Telemetry probes * Record to Legacy Telemetry by (where possible) using the [Glean Interface for Firefox Telemetry](https://firefox-source-docs.mozilla.org/toolkit/components/glean/user/gifft.html] or (where not possible) leaving the existing Telemetry API calls in place. * (we can remove any Legacy probes that only record in GVST mode (have `record_in_products: ["geckoview_streaming"]`). They never reported data via Telemetry: they only used Telemetry APIs to get to Fenix's Glean.) And then we can, on a more leisurely timeline, remove the GVST mechanism from both sides of JNI.
Bug 1877836 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
[Geckoview Streaming Telemetry](https://firefox-source-docs.mozilla.org/toolkit/components/telemetry/obsolete/geckoview-streaming.html) is an obsolete and deprecated module of Legacy Firefox Desktop Telemetry that allowed specific Histograms and Scalars recorded in Gecko to be relayed to geckoview-embedding applications (most notably Firefox for Android) so they could be reported by those embedding applications. It has been obsolete and deprecated since bug 1670261 allowed Gecko and Firefox for Android to share the same Glean. From then on, the best way to get your data to be recorded in Firefox Desktop and Firefox for Android has been to just use Glean. Recently we (Bas and Marc mostly) discovered in bug 1850847 that GVST has likely never worked fully on the release channel due to the Legacy Telemetry API throwing the data away because it was operating in non-unified mode. We need this data to help inform our decisions, so getting this working is of recent and increasing importance. Let's get this working by removing GVST while ensuring the continuity of data reported to Telemetry in Firefox Desktop and to Glean in Firefox for Android. We'll do this by migrating the GVST-using metrics to submit their data more directly: * Move the Fenix-only metrics definitions in `toolkit/components/telemetry/geckoview/streaming/metrics.yaml` to appropriate `metrics.yaml` files in the tree * Record to Glean by using Glean APIs at point of instrumentation of the GVST-using Legacy Telemetry probes * Record to Legacy Telemetry by (where possible) using the [Glean Interface for Firefox Telemetry](https://firefox-source-docs.mozilla.org/toolkit/components/glean/user/gifft.html) or (where not possible) leaving the existing Telemetry API calls in place. * (we can remove any Legacy probes that only record in GVST mode (have `record_in_products: ["geckoview_streaming"]`). They never reported data via Telemetry: they only used Telemetry APIs to get to Fenix's Glean.) And then we can, on a more leisurely timeline, remove the GVST mechanism from both sides of JNI.
[Geckoview Streaming Telemetry](https://firefox-source-docs.mozilla.org/toolkit/components/telemetry/obsolete/geckoview-streaming.html) is an obsolete and deprecated module of Legacy Firefox Desktop Telemetry that allowed specific Histograms and Scalars recorded in Gecko to be relayed to geckoview-embedding applications (most notably Firefox for Android) so they could be reported by those embedding applications. It has been obsolete and deprecated since bug 1670261 allowed Gecko and Firefox for Android to share the same Glean. From then on, the best way to get your data to be recorded in Firefox Desktop and Firefox for Android has been to just use Glean. Recently we (Bas and Marc mostly) discovered in bug 1850847 that GVST has likely never worked fully on the release channel due to the Legacy Telemetry API throwing the data away because it was operating in non-unified mode. We need this data to help inform our decisions, so getting this working is of recent and increasing importance. Let's get this working by removing GVST while ensuring the continuity of data reported to Telemetry in Firefox Desktop and to Glean in Firefox for Android. We'll do this by migrating the GVST-using metrics to submit their data more directly: * Move the Fenix-only metrics definitions in `toolkit/components/telemetry/geckoview/streaming/metrics.yaml` to appropriate `metrics.yaml` files in the tree * Record to Glean by using Glean APIs at point of instrumentation of the GVST-using Legacy Telemetry probes * Record to Legacy Telemetry by (where possible) using the [Glean Interface for Firefox Telemetry](https://firefox-source-docs.mozilla.org/toolkit/components/glean/user/gifft.html) or (where not possible) leaving the existing Telemetry API calls in place. * (we can remove any Legacy probes that only record in GVST mode (have `record_in_products: ["geckoview_streaming"]` (and _only_ `geckoview_streaming`)). They never reported data via Telemetry: they only used Telemetry APIs to get to Fenix's Glean.) And then we can, on a more leisurely timeline, remove the GVST mechanism from both sides of JNI.