Closed
Bug 1246178
Opened 9 years ago
Closed 8 years ago
Add FoxBox as a new product for Telemetry
Categories
(Cloud Services Graveyard :: Metrics: Pipeline, defect, P3)
Cloud Services Graveyard
Metrics: Pipeline
Tracking
(firefox47 affected)
RESOLVED
WONTFIX
Tracking | Status | |
---|---|---|
firefox47 | --- | affected |
People
(Reporter: Yoric, Unassigned)
References
Details
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?
Reporter | ||
Updated•9 years ago
|
Component: Telemetry Server → Metrics: Pipeline
Product: Webtools → Cloud Services
Summary: Add FoxLink as a new product for Telemetry → Add FoxBox as a new product for Telemetry
Version: Trunk → unspecified
Reporter | ||
Comment 1•9 years ago
|
||
Ah, I am informed that "FoxBox" is a better name.
Updated•9 years ago
|
Assignee: nobody → mreid
Points: --- → 1
Priority: -- → P2
Comment 3•9 years ago
|
||
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
Flags: needinfo?(mreid)
Comment 4•9 years ago
|
||
(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.
Reporter | ||
Comment 5•9 years ago
|
||
(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.
Updated•9 years ago
|
Priority: P2 → P3
Comment 6•9 years ago
|
||
This should roll into the Connected Devices telemetry per bug 1264055.
Assignee: mreid → nobody
Depends on: 1264055
Comment 7•8 years ago
|
||
Connected devices is not using fx data platform at this stage.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
Updated•6 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•