1246178 - Add FoxBox as a new product for Telemetry

Status: RESOLVED WONTFIX

(Cloud Services Graveyard :: Metrics: Pipeline, defect, P3)

Description

[David Teller [:Yoric] - still alive but not very active]

We are working on a new product that will need Telemetry. It is my understanding that we need to negotiate a unique id and an agreement with the server before we can start sending data.

The product name is FoxLink. What's the next step?

Comment 1

[David Teller [:Yoric] - still alive but not very active]

Ah, I am informed that "FoxBox" is a better name.

Comment 2

[David Teller [:Yoric] - still alive but not very active]

mreid, what do we need to do from here?

Comment 3

[Mark Reid [:mreid]]

Are you planning to send telemetry that is compatible with the Desktop telemetry format, semantics, and/or code[1]?  If so, it is a matter of updating the server config with a new "appName" for FoxBox so that it doesn't get bucketed into the "OTHER" category.

If you plan to report histograms and such, you will most likely want to follow the "main" ping format[2]. If not, you may want to use the simplified "core" ping format[3], or possibly invent a new ping type.

It is probably worth spending a bit of time on design for a document type that can be used as a basis for Telemetry for all the Connected Devices initiatives. What are critical things that need to be measured for all such initiatives? How will we report on them? What sort of app- or device-specific measurements will we need?

[1] https://gecko.readthedocs.org/en/latest/toolkit/components/telemetry/telemetry/common-ping.html
[2] https://gecko.readthedocs.org/en/latest/toolkit/components/telemetry/telemetry/main-ping.html
[3] https://gecko.readthedocs.org/en/latest/toolkit/components/telemetry/telemetry/core-ping.html

Comment 4

[Georg Fritzsche [:gfritzsche]]

(In reply to Mark Reid [:mreid] from comment #3)
> It is probably worth spending a bit of time on design for a document type
> that can be used as a basis for Telemetry for all the Connected Devices
> initiatives. What are critical things that need to be measured for all such
> initiatives? How will we report on them? What sort of app- or
> device-specific measurements will we need?

FWIW, we have a sync-up meeting with Connected Devices coming up on Feb 16, where i hope we can get a clearer understanding on this from a broader perspective.

Comment 5

[David Teller [:Yoric] - still alive but not very active]

(In reply to Mark Reid [:mreid] from comment #3)
> Are you planning to send telemetry that is compatible with the Desktop
> telemetry format, semantics, and/or code[1]?  If so, it is a matter of
> updating the server config with a new "appName" for FoxBox so that it
> doesn't get bucketed into the "OTHER" category.

We will use a new implementation, which we plan will use a format compatible with the Desktop format.

Once we are setup, we are going to report histograms (non-keyed and keyed). There are many fields in the main ping that don't make sense for us (e.g. flash version, chrome hangs, etc.)

> If you plan to report histograms and such, you will most likely want to
> follow the "main" ping format[2]. If not, you may want to use the simplified
> "core" ping format[3], or possibly invent a new ping type.
> 
> It is probably worth spending a bit of time on design for a document type
> that can be used as a basis for Telemetry for all the Connected Devices
> initiatives. What are critical things that need to be measured for all such
> initiatives? How will we report on them? What sort of app- or
> device-specific measurements will we need?

Good idea, if you wish to open such a document, we can start braindumping on it.

Comment 6

[Mark Reid [:mreid]]

This should roll into the Connected Devices telemetry per bug 1264055.

Comment 7

[Katie Parlante]

Connected devices is not using fx data platform at this stage.