Resurrect telemetry for http response codes (redirects)
Categories
(Core :: Networking, task, P5)
Tracking
()
Tracking | Status | |
---|---|---|
firefox72 | --- | fixed |
People
(Reporter: ckerschb, Assigned: ckerschb)
References
Details
(Whiteboard: [necko-triaged])
Attachments
(2 files)
47 bytes,
text/x-phabricator-request
|
Details | Review | |
2.32 KB,
text/plain
|
chutten
:
data-review+
|
Details |
Assignee | ||
Comment 1•6 years ago
|
||
Assignee | ||
Comment 2•6 years ago
|
||
Comment on attachment 9103978 [details]
Bug 1591131: Resurrect telemetry for http response codes (redirects).r=valentin
We have been collecting about status response codes before, but apparently I forgot to renew them. Do I need to fill out more information or are we good given that we have collected that information before?
Comment 3•6 years ago
|
||
Comment on attachment 9103978 [details]
Bug 1591131: Resurrect telemetry for http response codes (redirects).r=valentin
New and expanded data collections need Data Collection Review. Expanding the timeframe of collection counts as expansion, so we're going to need a fresh review.
(( reasons behind this include that the landscape of other collections has changed in the interim, so maybe there's some intersectional reason for regarding these more strictly. Also, our own understanding of what is and isn't acceptable collection changes over time. Eventually I expect there to be a short-form for renewing/reviving existing data collections, but for now we just have the one review process ))
Updated•6 years ago
|
Assignee | ||
Comment 4•6 years ago
|
||
Comment 5•6 years ago
|
||
Comment 7•6 years ago
|
||
bugherder |
Description
•