Provide built-in reasons identifying pings sent manually during debug
Categories
(Data Platform and Tools :: Glean: SDK, enhancement, P4)
Tracking
(Not tracked)
People
(Reporter: Dexter, Unassigned)
Details
When pings are submitted using our debug tools (e.g. to show up in the debug view) they will be sent without a ping_info.reason.
We should consider providing a ping reason that we automatically add in these cases, for example glean.debug or something.
Comment 1•3 years ago
|
||
Note that there is logic to prevent the use of un-defined ping reasons that will rewrite it to None. If we go with glean.debug and try to make special cases out of glean.* reasons, we should forbid the manual inclusion of glean.* reasons in glean_parser as well as in the SDKs.
Comment 2•3 years ago
|
||
The absence of a reason identifies manually triggered pings already (for built-in pings).
This is thus not super important to change.
Comment 3•3 years ago
•
|
||
Since the ultimate cause of a ping with no reason cannot be distinguished between "debug" and "this is probably a bug", we should still add a reason, in my opinion.
Comment 4•2 months ago
|
||
closing this as stale/wontfix
Description
•