Skip to content
This repository has been archived by the owner on Feb 20, 2023. It is now read-only.

[Telemetry] Adding user-specified search engines #5884

Closed
vesta0 opened this issue Oct 9, 2019 · 3 comments
Closed

[Telemetry] Adding user-specified search engines #5884

vesta0 opened this issue Oct 9, 2019 · 3 comments
Assignees
Labels
E3 Estimation Point: average, 2 - 3 days eng:qa:verified QA Verified eng:ready Ready for engineering Feature:SearchProvider Feature:Telemetry
Milestone

Comments

@vesta0
Copy link
Collaborator

vesta0 commented Oct 9, 2019

Description & Product Manager / Data Scientist User Story

  • As a product owner, I want to know if people type use feature X so I can..

I can add a custom search engine in Fenix.
I can remove a custom search engine from my list of search engines

Hypothesis

What questions will you answer with this data?

How often user add or use other search engines not listed?

Why does Mozilla need to answer these questions?

Determine how to better integrate frequently used features within the product.

What probes (suggested, if applicable)

  • User adding a new custom search engine (we don't want to track the name of the search engine)
  • User deleting a custom search engine
  • Searches performed with a custom search engine

Acceptance Criteria (Added by PM)

  • Event pings can be queried via re:dash
  • We are sending telemetry events for the actions listed in the requirements
  • We have documented the telemetry
  • We have asked a data steward to review the telemetry
  • NOT an AC: Data science to create dashboard or further graphs (this will be a separate issue, this issue is only about hooking up the events described and that they can be queried in re-dash)

┆Issue is synchronized with this Jira Task

@vesta0 vesta0 added this to Prioritized Feature Backlog in Fenix Sprint Kanban Oct 9, 2019
@vesta0 vesta0 added the must label Oct 9, 2019
@vesta0 vesta0 added the E3 Estimation Point: average, 2 - 3 days label Oct 16, 2019
@vesta0 vesta0 added should and removed must labels Nov 7, 2019
@vesta0 vesta0 moved this from Must to Should in Fenix Q4 Feature Backlog Nov 7, 2019
@liuche liuche added the eng:ready Ready for engineering label Nov 22, 2019
@ValentinTimisica ValentinTimisica self-assigned this Nov 28, 2019
@ValentinTimisica ValentinTimisica moved this from Prioritized Feature Backlog to Sprint Backlog in Fenix Sprint Kanban Dec 3, 2019
@ValentinTimisica ValentinTimisica moved this from Sprint Backlog to In Progress in Fenix Sprint Kanban Dec 3, 2019
ValentinTimisica added a commit to ValentinTimisica/fenix that referenced this issue Dec 3, 2019
Created events for adding and deleting a custom search engine and for searches
performed with a custom search engine.
ValentinTimisica added a commit to ValentinTimisica/fenix that referenced this issue Dec 4, 2019
Created events for adding and deleting a custom search engine and for searches
performed with a custom search engine.
ValentinTimisica added a commit to ValentinTimisica/fenix that referenced this issue Dec 4, 2019
@liuche liuche moved this from In Progress to In Dev Review in Fenix Sprint Kanban Dec 5, 2019
ValentinTimisica added a commit to ValentinTimisica/fenix that referenced this issue Dec 5, 2019
Created events for adding and deleting a custom search engine and for searches
performed with a custom search engine.
ValentinTimisica added a commit to ValentinTimisica/fenix that referenced this issue Dec 5, 2019
ValentinTimisica added a commit to ValentinTimisica/fenix that referenced this issue Dec 6, 2019
Created events for adding and deleting a custom search engine and for searches
performed with a custom search engine.
ValentinTimisica added a commit to ValentinTimisica/fenix that referenced this issue Dec 6, 2019
ValentinTimisica added a commit to ValentinTimisica/fenix that referenced this issue Dec 10, 2019
Created events for adding and deleting a custom search engine and for searches
performed with a custom search engine.
ValentinTimisica added a commit to ValentinTimisica/fenix that referenced this issue Dec 10, 2019
ValentinTimisica added a commit to ValentinTimisica/fenix that referenced this issue Dec 18, 2019
Created events for adding and deleting a custom search engine and for searches
performed with a custom search engine.
ValentinTimisica added a commit to ValentinTimisica/fenix that referenced this issue Dec 18, 2019
ValentinTimisica added a commit to ValentinTimisica/fenix that referenced this issue Dec 19, 2019
Created events for adding and deleting a custom search engine and for searches
performed with a custom search engine.
ValentinTimisica added a commit to ValentinTimisica/fenix that referenced this issue Dec 19, 2019
boek pushed a commit that referenced this issue Jan 13, 2020
Created events for adding and deleting a custom search engine and for searches
performed with a custom search engine.
boek pushed a commit that referenced this issue Jan 13, 2020
@ValentinTimisica ValentinTimisica moved this from In Dev Review to Ready for QA in Fenix Sprint Kanban Jan 16, 2020
@liuche liuche mentioned this issue Jan 22, 2020
32 tasks
@liuche liuche added this to the v3.2 milestone Jan 22, 2020
@AndiAJ
Copy link
Collaborator

AndiAJ commented Jan 23, 2020

Hi, I've just checked this matter on the latest Fenix Beta 3.2.0-beta. 2 #20230233 from 01/23 using a OnePlus A3 (Android 6).

✔️User adding a new custom search engine - Ping 7f01f061-7c25-4c78-9b8c-0bfda6f13cec

Searches performed with a custom search engine.

► Set Custom Search Engine as Default
✔️Baseline ping after performing a search - Ping a1b344af-706e-4dd4-9201-f7b9a0fe8170
✔️Baseline ping after performing a search using a suggestion - Ping 12cb6787-b924-418e-9713-b6fe6e30e7ee

► Using the Custom Search Engine from the Shortcuts section.
✔️ Event type ping after performing a search - Ping 83198118-0d46-4b41-b47b-3c70186e92b8
✔️ Baseline ping after performing a search - Ping cc597e31-0b5b-452b-a3be-6a05e4831f8f

✔️ Event type ping after performing a search using a suggestion - Ping c4f11088-c226-43eb-8abe-9387822b9b44
✔️Baseline ping after performing a search using a suggestion - Ping a2302f58-ba53-482e-8ae1-d1bda3a66ee7

❌ User deleting a custom search engine - NO ping is generated

Logcat
Glean dashboard

@vesta0 & @liuche - When performing a search (default.action or default.suggestion) using the default search engine, the event type ping doesn't contain any information about used search engine.

On the other hand, when the user uses a search engine from the shortcuts section, the engine name is displayed in the events type ping.

Wouldn't it be better to also include the search engine name in the event type ping when a user performs a search using the default search engine?

E.g.
• Event type ping after performing a search with the default search engine

{
          "category": "events",
          "extra": {
            "source": "default.action"
          },
          "name": "performed_search",
          "timestamp": 7841
        }

• Event type ping after performing a search using a suggestion with the default search engine

  {
          "category": "events",
          "extra": {
            "source": "default.suggestion"
          },
          "name": "performed_search",
          "timestamp": 7741
        }

I'll remove the QA needed label until further notice.

@ValentinTimisica
Copy link
Contributor

@AndiAJ note that this issue is tied to #7751 (which is a follow up to this telemetry task) and you should test the build generated after 7751 was merged because there I removed the "Searches performed with a custom search engine" telemetry (see explanation in all the comments from here).

So actually these 2 tasks only register events for adding and deleting a custom search engine (not for searching with it).

Regarding the deletion event not being send, it is indeed a bug and I created a new issue for it (#7881).

@AndiAJ
Copy link
Collaborator

AndiAJ commented Jan 23, 2020

Hi, based on @ValentinTimisica 's comment, I'll mark this issue verified as fixed.

  1. The user adding a new custom search engine work properly
  2. The user deleting a custom search engine will be tracked in [Bug] Telemetry event for deleting a custom search engine is not sent #7881

@AndiAJ AndiAJ closed this as completed Jan 23, 2020
Fenix Q4 Feature Backlog automation moved this from Should to Done! Jan 23, 2020
@project-bot project-bot bot moved this from Ready for QA to Sprint 20.2 Done in Fenix Sprint Kanban Jan 23, 2020
@AndiAJ AndiAJ added the eng:qa:verified QA Verified label Jan 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
E3 Estimation Point: average, 2 - 3 days eng:qa:verified QA Verified eng:ready Ready for engineering Feature:SearchProvider Feature:Telemetry
Projects
No open projects
Development

No branches or pull requests

4 participants