Closed Bug 1600986 Opened 4 years ago Closed 4 years ago

duckduckgo has two names in about:telemetry

Categories

(Firefox :: Search, defect)

defect
Not set
normal

Tracking

()

RESOLVED WONTFIX
Tracking Status
firefox71 --- wontfix
firefox72 --- wontfix
firefox73 --- wontfix

People

(Reporter: ccomorasu, Unassigned)

Details

Affected versions

  • Fx 73.0a1
  • Fx 72.0b2
  • Fx 71.0

Affected platforms

  • Windows 10 x64
  • macOS 10.14
  • Ubuntu 18.04 LTS

Steps to reproduce

  1. Launch Firefox.
  2. Go to about:preferences#search and activate the search bar.
  3. Perform searches using the following methods:
  • using the url bar
  • using the search bar
  • using the new tab page
  • using the context menu
  1. Go to about telemetry, select Raw JSON, then select Raw Data.
  2. Search for "SEARCH_COUNTS".

Expected result

  • The searches from step 3 are displayed with the same name/abbreviation.

Actual result

  • Context menu, new tab and search bar searches are abbreviated as ddg, while the rest are named duckduckgo.

Regression range
I will return with the regression window ASAP.

Has Regression Range: --- → no
Has STR: --- → yes

Please can you add a little more detail here? Exactly which interactions are abbreviated and which ones are not?

For each search, there should be a ddg.<location> (e.g. ddg.urlbar) and a duckduckgo.in-content:sap:<code> logged.

As far as I can tell, that hasn't changed for quite a while.

Flags: needinfo?(cristian.comorasu)

These probes are abbreviated as ddg:

  • context menu search
  • search bar search
  • new tab search
  • url bar search

The following probes are written as duckduckgo:

  • in-content:organic:h_
  • in-content:organic:sap:ffcm
  • in-content:organic:sap:ffab
  • in-content:organic:sap:ffsb
  • in-content:organic:sap:ffnt

Is this difference between the duckduckgo probes intended?

Flags: needinfo?(cristian.comorasu)

The context/search/new tab/url bar search probes have used ddg (ddg.urlbar etc) since before Firefox 50. The in-content probes have used duckduckgo since they were added afaict (somewhere between 60 & 66).

Although this is inconsistent, I'm assuming that our dashboards are already set up to handle these since metrics & management haven't been complaining.

Whilst this isn't ideal from a testing perspective I don't think we can justify changing it at this time. There is future work that I'm hoping for, e.g. bug 1605164, that would fix some of the inconsistencies in the code and as a side effect, force us to fix this.

Hence marking as wontfix, as these are the way they are since they were created and we're not currently intending on changing them.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX

Bugbug thinks this bug is a regression, but please revert this change in case of error.

Keywords: regression
You need to log in before you can comment on or make changes to this bug.