-
Notifications
You must be signed in to change notification settings - Fork 113
Create an "activity-stream-newtab" source for Search Telemetry #2729
Comments
Yea I would agree with dzeber that we probably don't want to mess with search telemetry for new tab since it could affect analysis being done on that. On the other hand, do we need UT telemetry for Activity Stream search at all? If it's any easier to just not send UT for AS search perhaps that could be better since we are collecting metrics via onyx |
In that case (which is actually probably preferable) we could just add the source in BrowserUsageTelemetry so it gets picked up and then literally just do nothing when we get that action |
It seems like we'd have to talk to the metrics folks before turning off that data flow -- I suspect they're comparing search sources across a whole variety of things, and they probably want to continue to do that even after tiles goes away. |
There is now a bugzilla bug for this in order to get more info from people. I'm sure there will be a discussion around this. |
This will need to handle |
I've had a new idea for this where I would disable preloading in the test setup so that we don't have to close the tab to open a new one to ensure we don't get a preloaded Activity Stream tab. Update: that second approach also doesn't work. |
I'm assuming this was closed because this is no longer desired? |
Also see https://bugzilla.mozilla.org/show_bug.cgi?id=1381460
When we switched over our search component to recycle the existing one in about:newtab and about:home (https://github.com/mozilla/activity-stream/blob/master/system-addon/content-src/components/Search/Search.jsx#L26-L32) we see that we pass in "newtab" as the HealthReportKey. We did this in order to fix a failing test where we were originally passing in "activity" as a source, which wasn't recognized in BrowserUsageTelemetry.jsm as a valid source, and therefore we never added the appropriate Telemetry Probe, and failed some tests. The concern @dmose and I had was that by re-using the "newtab" source, we essentially mix up the data for searches that come in from tiles newtab with activity stream's newtab, since their sources are the same. At the time, @dmose and I weren't sure about how much engineering effort it would take to create a new source, so we decided to leave it as "newtab" for now.
After chatting with the folks in #fx-metrics on slack about this, we were told we probably need to add our own "activity-stream-newtab" source, since we definitely want to separate out the experience of activity stream vs current newtab. Georg Fritzsche is the guy we want to ask about what kind of engineering work is involved for adding a new source. At a minimum, we guess we have to add it to this list: https://dxr.mozilla.org/mozilla-central/source/browser/modules/BrowserUsageTelemetry.jsm#42, and possibly handle it differently here: https://dxr.mozilla.org/mozilla-central/source/browser/modules/BrowserUsageTelemetry.jsm#444, but we should ask Georg about what other work needs to be done to add it properly.
So, does this block preff-ing on in 56 for some users? Quoted by David Zeber on slack:
cc @Mardak @emtwo @k88hudson
The text was updated successfully, but these errors were encountered: