write_in_microsurvey ping instructions are being forwarded in a clunky way
Categories
(Firefox :: Messaging System, enhancement)
Tracking
()
People
(Reporter: aminomancer, Assigned: aminomancer)
References
(Blocks 3 open bugs)
Details
(Whiteboard: [omc])
Attachments
(2 files, 1 obsolete file)
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-beta+
|
Details | Review |
The way we decide whether to record messaging system metrics on the messaging-system ping or the microsurvey ping involves reading the message's write_in_microsurvey property. Right now, that property is being read by the React component and passed all the way through the nested components, where it gets added to the new telemetry event's event_context, which is passed to MultiStageUtils.sendEventTelemetry(), ultimately reaching AboutWelcomeTelemetry.sendTelemetry, which processes it and decides to record the metrics on microsurvey as a result.
This is a pretty clunky and inefficient way of doing things. It didn't occur to me at the time that we could bypass React entirely. The surface code that instantiates the React component is aware of the message definition - it's what is passing the message to the React component via AWGetFeatureConfig(). Likewise, it is what provides the AWSendEventTelemetry method. So it can easily check the write_in_microsurvey property within AWSendEventTelemetry, and insert it into the event_context when applicable. That minimizes the amount of processing for the property.
Updated•3 months ago
|
| Assignee | ||
Comment 1•3 months ago
|
||
Stop passing write_in_microsurvey from AWGetFeatureConfig to the
AWSendEventTelemetry call. Instead, the surface that provides the
AWSendEventTelemetry method will just insert it in the method
definition and pass it straight to AboutWelcomeTelemetry. This means
the React component does not have to be aware of the property at all.
Updated•3 months ago
|
Comment 4•3 months ago
|
||
Backed out for causing bc failures @ browser_aiwindow_smartbar_telemetry
Backout link: https://hg.mozilla.org/integration/autoland/rev/0cfba7541c6983a197b31a609ae128a69c5af779
Comment 6•3 months ago
|
||
| bugherder | ||
Stop passing write_in_microsurvey from AWGetFeatureConfig to the
AWSendEventTelemetry call. Instead, the surface that provides the
AWSendEventTelemetry method will just insert it in the method
definition and pass it straight to AboutWelcomeTelemetry. This means
the React component does not have to be aware of the property at all.
Original Revision: https://phabricator.services.mozilla.com/D301946
Updated•3 months ago
|
Updated•3 months ago
|
Comment 8•3 months ago
|
||
:aminomancer, the uplift request is missing an uplift request form
https://wiki.mozilla.org/Release_Management/Requesting_an_Uplift#Submit_the_Uplift_Request_Form
Comment 10•3 months ago
|
||
Stop passing write_in_microsurvey from AWGetFeatureConfig to the
AWSendEventTelemetry call. Instead, the surface that provides the
AWSendEventTelemetry method will just insert it in the method
definition and pass it straight to AboutWelcomeTelemetry. This means
the React component does not have to be aware of the property at all.
Original Revision: https://phabricator.services.mozilla.com/D301946
Updated•3 months ago
|
Updated•3 months ago
|
Updated•3 months ago
|
Updated•3 months ago
|
Comment 11•3 months ago
|
||
| uplift | ||
Updated•3 months ago
|
Updated•3 months ago
|
Comment 12•3 months ago
|
||
| uplift | ||
Comment 13•3 months ago
|
||
| uplift | ||
Comment 14•3 months ago
|
||
Backed out of release, since Bug 2036193 had to be backout due to CI failures
Updated•3 months ago
|
Updated•3 months ago
|
Updated•3 months ago
|
Updated•3 months ago
|
Updated•3 months ago
|
Description
•