777213 - Missing chrome hang reports?

Status: RESOLVED FIXED

(Mozilla Metrics :: Data/Backend Reports, defect)

Description

[Vladan Djeric (:vladan)]

I am wondering why the first batch of chrome-hang data (METRICS-663) had more hang reports than the second (METRICS-827), despite more users having hang reporting capability during the second reporting period? 
Is it a matter of Telemetry opt-in rates? Data loss?

The first batch of chromehang data (METRICS-663) was generated by a dozen users of the nightly-profiling branch.
- It covered the 59 day period of April 1st to May 29th
- It had 42 Telemetry reports with 109 individual hang stacks
- This averages to 1.85 hangs reported/day

The second batch of chromehang data (METRICS-827) was mostly generated by users of our regularly Nightly branch after we turned on frame-pointers & hang reporting in the regular Nightly channel on June 18th (bug 764216).
- This batch of data covered the 44 day period from June 10th to July 23rd
- It had 27 unique* Telemetry reports and 40 individual hang stacks
- This averages to 0.91 hangs reported/day

I would have expected the daily average for the second batch to be much higher.


* Note that some telemetry pings are repeated on separate days in this batch, e.g. ping with ID 537e23e0-2611-4d68-8fed-dac86c177104 appears both on July 4th & July 6th

Comment 1

[Annie Elliott]

https://metrics.mozilla.com/projects/browse/METRICS-985

Comment 2

[Vladan Djeric (:vladan)]

This has been resolved, we were getting chrome-hang reports from the nightly-profiling branch instead of the nightly branch.