Confirmed users
381
edits
Performance/Telemetry: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 40: | Line 40: | ||
*telemetry.success (No, Yes) - Whether the past telemetry pings succeeded 1:No 2:Yes. | *telemetry.success (No, Yes) - Whether the past telemetry pings succeeded 1:No 2:Yes. | ||
= Metrics Presentation = | |||
== General Summary/Graphs == | |||
* geo-io location info | |||
* locale | |||
* Firefox version | |||
* Operating system | |||
* device | |||
* ram | |||
* cpu | |||
== Histograms == | |||
Histograms are submitted as {name, range:[min,max], type, sum, values:{"0":x, ... n:y}}. They should be aggregated with name + histogram parameters forming a unique id. | |||
== Filtering == | |||
The ui should provide a filtering capability. For example we should be able to filter inputs going into histogram aggregations by the fields listed in "General Summary/Graphs". Furthermore it would be useful to filter by other histograms, ie "only include entries where histograms contain entires in the x-y range". | |||
== Trending == | |||
It would be nice to provide tracking of telemetry values and notify developers of changes in trends, "ie memory usage went up by 5-10mb in build x vs y". | |||