Collect telemetry for request time and cache age for Pocket
Categories
(Firefox :: New Tab Page, defect, P1)
Tracking
()
People
(Reporter: k88hudson, Assigned: nanj)
References
Details
(Keywords: github-merged)
Attachments
(8 files, 1 obsolete file)
52 bytes,
text/x-github-pull-request
|
Details | Review | |
1.89 KB,
text/plain
|
klong
:
data-review+
klong
:
review+
|
Details |
1.56 KB,
text/plain
|
klong
:
data-review+
klong
:
review+
|
Details |
1.31 MB,
image/png
|
Details | |
47 bytes,
text/x-phabricator-request
|
lizzard
:
approval-mozilla-beta+
|
Details | Review |
785.94 KB,
image/png
|
Details | |
842.36 KB,
image/png
|
Details | |
924.97 KB,
image/png
|
Details |
Due to Product's feedback that performance and content freshness will have an impact on experiment success, we would like to capture the following information:
- Request time for layout endpoint
- Request time for feed endpoints
- Request time for spoc endpoint
- Total request time for data completeness / time to first render (do we already have this?)
- Cache age on browser start-up
Reporter | ||
Updated•5 years ago
|
Reporter | ||
Updated•5 years ago
|
Assignee | ||
Comment 1•5 years ago
|
||
k88hudson - are we only interested in the first round of endpoint requests on browser start-up, or do we also want to collect the request time for all the subsequent requests?
Reporter | ||
Comment 2•5 years ago
|
||
I think we only care about the first round after the start-up of the browser.
Comment 3•5 years ago
|
||
Updated•5 years ago
|
Assignee | ||
Comment 4•5 years ago
|
||
Hey Kenny, could you do a data review for us? See the attachment for the data review request form.
Thanks!
Assignee | ||
Comment 5•5 years ago
|
||
Updated•5 years ago
|
Comment 7•5 years ago
|
||
Reporter | ||
Comment 8•5 years ago
|
||
Nan, can you add steps to verify to this bug and needinfo brahmini when you've posted them? Thanks
Assignee | ||
Comment 9•5 years ago
|
||
I've updated the QA document with details about the test plan.
Brahmini, you can find it in the "Performance pings" section of the "QA plan for Pocket + New Tab Experiment".
Comment 10•5 years ago
•
|
||
Hi, I can find it in QA Plan https://docs.google.com/document/d/1iySmNA2tBl3ApLuJtP7UBlPwNx9sH1SmK-jG6exvMQ0/edit#heading=h.3zj0kjmo4xno.Thanks.
Comment 11•5 years ago
|
||
Following steps as per QA plan for Pocket + New Tab Experiment
doc
I used 2 different end-points for pref browser.newtabpage.activity-stream.discoverystream.config
:
- {"enabled":true,"show_spocs":true,"layout_endpoint":"https://getpocket.com/v3/newtab/layout?version=1&consumer_key=40249-e88c401e1b1f2242d9e441c4&layout_variant=dev-test-all1"} and
- {"enabled":true,"show_spocs":true,"layout_endpoint":"https://getpocket.com/v3/newtab/layout?version=1&consumer_key=40249-e88c401e1b1f2242d9e441c4&layout_variant=dev-test-all2"}
Cache age request is missing. (can be found in attachment)
Attachment QA - bug 1525391.png
Please let me know if I'm missing anything, thanks.
Assignee | ||
Comment 12•5 years ago
|
||
Hi Brahmini,
Thanks for pointing this out! The cache age will only be reported if there exists a cache file. There are two cases where the cache file won't exist:
- When you create a Firefox profile
- When you change anything of the discovery stream pref, which will delete the old cache file
I will put this to the QA document.
BTW, looks like both endpoints in comment 11 are broken in the nightly. I am getting these errors:
Failed to fetch https://getpocket.com/v3/newtab/layout?version=1&consumer_key=40249-e88c401e1b1f2242d9e441c4&layout_variant=dev-test-all1: https://getpocket.com/v3/newtab/layout?version=1&consumer_key=40249-e88c401e1b1f2242d9e441c4&layout_variant=dev-test-all1 returned unexpected status: 400 DiscoveryStreamFeed.jsm:97
No response for response.layout prop DiscoveryStreamFeed.jsm:166
Failed to fetch https://getpocket.com/v3/newtab/layout?version=1&consumer_key=40249-e88c401e1b1f2242d9e441c4&layout_variant=dev-test-all1: https://getpocket.com/v3/newtab/layout?version=1&consumer_key=40249-e88c401e1b1f2242d9e441c4&layout_variant=dev-test-all1 returned unexpected status: 400 DiscoveryStreamFeed.jsm:97
No response for response.layout prop
Reporter | ||
Comment 13•5 years ago
|
||
Reporter | ||
Comment 14•5 years ago
|
||
Ok, can you review the uplift patch and make the uplift form request?
Comment 15•5 years ago
|
||
Comment on attachment 9044255 [details]
Bug 1525391 - Collect telemetry for request time and cache age for Pocket
Beta/Release Uplift Approval Request
Feature/Bug causing the regression
None
User impact if declined
the product team will be unable to verify the performance of the new tab page in the field, possibly leading to undetected poor performance profile
Is this code covered by automated tests?
Yes
Has the fix been verified in Nightly?
Yes
Needs manual test from QE?
Yes
If yes, steps to reproduce
(see comment #11)
List of other uplifts needed
None
Risk to taking this patch
Low
Why is the change risky/not risky? (and alternatives if risky)
this code is an extension to existing telemetry, and any errors raised will not be user facing
String changes made/needed
Assignee | ||
Updated•5 years ago
|
Comment 16•5 years ago
|
||
QA Results:
Tested on :
FF Nightly version : 67.0a1 (2019-02-15)
OS : Mac and Windows 10 Pro
Results attached QA Results - bug 1525391 (Mac OS).png
Works as expected.
Marking as verified.
Updated•5 years ago
|
Updated•5 years ago
|
Comment 17•5 years ago
|
||
Comment on attachment 9044255 [details]
Bug 1525391 - Collect telemetry for request time and cache age for Pocket
Planned work for pocket/new tab. Verified in Nightly.
OK for beta uplift, should land for beta 9.
Landing order: bug 1519879, bug 1525494, bug 1526861, bug 1524669, bug 1527195, bug 1525391, bug 1527347, bug 1525366, bug 1527626, bug 1527397, bug 1518258, bug 1527701, bug 1527370.
Comment 18•5 years ago
|
||
bugherder uplift |
Comment 19•5 years ago
|
||
(In reply to Brahmini Nagabandi from comment #16)
Created attachment 9044324 [details]
QA Results - bug 1525391 (Mac OS).pngQA Results:
Tested on :
FF Nightly version : 67.0a1 (2019-02-15)
OS : Mac and Windows 10 ProResults attached
QA Results - bug 1525391 (Mac OS).png
Works as expected.
Marking as verified.
Can you please verify this issue on Firefox 66 Beta 9 (https://archive.mozilla.org/pub/firefox/candidates/66.0b9-candidates/build1/)?
Comment 20•5 years ago
•
|
||
BETA Testing:
QA Results:
Tested on :
FF Beta version : 66.0b9 (64-bit)
OS : Mac and Windows 10 Pro
Date : Feb 22
End-point used : {"api_key_pref":"extensions.pocket.oAuthConsumerKey","enabled":true,"show_spocs":true,"layout_endpoint":"https://getpocket.com/v3/newtab/layout?version=1&consumer_key=$apiKey&layout_variant=66-beta-2-complex"}
Verified on the latest Beta. Works as expected.
Attaching QA results below for both Mac and Windows
Marking as verified.
Comment 21•5 years ago
|
||
Comment 22•5 years ago
|
||
Updated•5 years ago
|
Updated•5 years ago
|
Description
•