Open
Bug 711087
Opened 14 years ago
Updated 3 years ago
Add telemetry probes for page loads and crashes
Categories
(Firefox :: General, defect)
Firefox
General
Tracking
()
NEW
People
(Reporter: akeybl, Unassigned)
References
(Depends on 1 open bug)
Details
(Whiteboard: [notacrash])
We'd like to add telemetry probes for the following two metrics:
* Number of page loads since last ping
* Number of crashes since last ping
These numbers should be aggregated and sent back to us on a daily basis, or whenever the browser is opened up next after 24 hours. Once the numbers have been sent, they can be reset and re-incremented over the next period.
For what constitutes a page load, we'd like to keep parity with the chromium project. The metrics code is our first lead..
https://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/metrics/metrics_service.cc - MetricsService::LogLoadStarted()
which means that for wherever they send the NOTIFICATION_LOAD_START event, we need to find a way to also increment our page load value in Firefox.
| Reporter | ||
Comment 1•14 years ago
|
||
The plan is to also collect this data for all Firefox users in the future, piggy-backing on the new metrics ping (bug 697724).
| Reporter | ||
Comment 2•14 years ago
|
||
Ted/bz - do you know who may be in the best position to implement this probe?
Comment 3•14 years ago
|
||
For starters, someone who has time to figure out what NOTIFICATION_LOAD_START means in Chrome....
Updated•14 years ago
|
Assignee: nobody → jschoenick
| Reporter | ||
Comment 4•14 years ago
|
||
Separated
(In reply to Alex Keybl [:akeybl] from comment #0)
> * Number of crashes since last ping
out into bug 715362, but leaving the Summary the same as we still want both metrics sent together rather than being aggregated separately.
Updated•14 years ago
|
Whiteboard: [notacrash]
Comment 5•4 years ago
|
||
The bug assignee didn't login in Bugzilla in the last 7 months, so the assignee is being reset.
Assignee: john → nobody
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•