Instrument when we reject re-adding an already in-flight ping
Categories
(Data Platform and Tools :: Glean: SDK, defect, P3)
Tracking
(Not tracked)
People
(Reporter: janerik, Assigned: chutten)
Details
Attachments
(2 files)
2.49 KB,
text/plain
|
charlie
:
data-review+
|
Details |
42 bytes,
text/x-github-pull-request
|
Details | Review |
We now reject attempts to re-enqeue pings we are tracking as in-flight (by their doc ID).
We should instrument this failure case to ensure we're not dropping data.
Updated•2 years ago
|
Reporter | ||
Updated•2 years ago
|
Assignee | ||
Comment 1•2 years ago
|
||
Comment 2•2 years ago
•
|
||
Comment on attachment 9318271 [details]
data collection review request
Data Review
-
Is there or will there be documentation that describes the schema for the ultimate data set in a public, complete, and accurate way?
Yes, via the Glean Dictionary -
Is there a control mechanism that allows the user to turn the data collection on and off?
Yes, the standard telemetry opt-out found within our applications -
If the request is for permanent data collection, is there someone who will monitor the data over time?
It is permanent, and will be monitored by chutten@mozilla.com as an individual, and glean-team@mozilla.com as a team -
Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under?
Category 1, technical data -
Is the data collection request for default-on or default-off?
default-on -
Does the instrumentation include the addition of any new identifiers (whether anonymous or otherwise; e.g., username, random IDs, etc. See the appendix for more details)?
No -
Is the data collection covered by the existing Firefox privacy notice?
Yes -
Does the data collection use a third-party collection tool?
No
Assignee | ||
Comment 3•2 years ago
|
||
Assignee | ||
Comment 4•2 years ago
|
||
chutten merged PR #2381: "bug 1816401 - Instrument the count of dropped in-flight pings" in cac6602.
Description
•