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

Telemetry for QR Scanner #1857

Closed
colintheshots opened this issue Apr 20, 2019 · 7 comments
Closed

Telemetry for QR Scanner #1857

colintheshots opened this issue Apr 20, 2019 · 7 comments
Assignees
Labels

Comments

@colintheshots
Copy link
Contributor

colintheshots commented Apr 20, 2019

As a product owner, I want to know how often people use the QR code scanner to search and open URLs.

Added by @bbinto, April 29, 2019

What questions will you answer with this data?

  • These probes will help us understand if users use the QR code scanner and how useful it is (# of times successful prompt shown to proceed/open the URL

Probes

  • Clicked QR scan button in search bar
  • Capture event when prompt shows up that reading was successful / not successful

Dependencies (Added by PM and Eng)

  • Glean SDK (Event ping)

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
Copy link
Collaborator

vesta0 commented Apr 23, 2019

@bbinto to fill out requirements :)

@vesta0 vesta0 added P1 Current sprint Feature:Telemetry labels Apr 23, 2019
@vesta0 vesta0 added this to the MVP Backlog milestone Apr 23, 2019
@bbinto
Copy link
Contributor

bbinto commented Apr 29, 2019

@vesta0 - updated

@bbinto bbinto removed their assignment Apr 29, 2019
@vesta0 vesta0 added P2 Upcoming release and removed P1 Current sprint labels May 8, 2019
@vesta0 vesta0 added this to High priority backlog (not in the current sprint) in Fenix Sprint Kanban May 8, 2019
@bifleming bifleming removed this from High priority backlog (not in the current sprint) in Fenix Sprint Kanban May 8, 2019
@sblatz sblatz self-assigned this May 15, 2019
sblatz added a commit to sblatz/fenix that referenced this issue May 15, 2019
sblatz added a commit to sblatz/fenix that referenced this issue May 15, 2019
sblatz added a commit to sblatz/fenix that referenced this issue May 15, 2019
sblatz added a commit to sblatz/fenix that referenced this issue May 15, 2019
boek pushed a commit that referenced this issue May 17, 2019
@vesta0 vesta0 added this to In Progress in Fenix Sprint Kanban May 17, 2019
@bifleming bifleming added the Release Blocker Blocks a Release label May 17, 2019
@sblatz sblatz added eng:qa:needed QA Needed and removed in progress labels May 17, 2019
@project-bot project-bot bot moved this from In Progress to Ready for QA in Fenix Sprint Kanban May 17, 2019
@bsurd
Copy link

bsurd commented May 28, 2019

No metrics are logged in the glean dashboard for the QR code scanner. According to the metrics.yaml file values should be logged for when the scanner has been opened, for the navigation prompt and whether navigation has been allowed or denied.

Edit: Telemetry for the QR scanner is displayed. Was confused by the fact that the data was in the metrics section on the file, but it is mentioned that it's of type event.

@bsurd bsurd added eng:qa:verified QA Verified and removed eng:qa:needed QA Needed labels May 28, 2019
@bsurd bsurd closed this as completed May 28, 2019
@bsurd bsurd moved this from Ready for QA to Done in Fenix Sprint Kanban May 28, 2019
@sblatz
Copy link
Contributor

sblatz commented May 28, 2019

Telemetry for the QR scanner is displayed. Was confused by the fact that the data was in the metrics section on the file, but it is mentioned that it's of type event.

@boek is this a problem or is that expected?

@bsurd
Copy link

bsurd commented May 28, 2019

To be clear I've referring to the metrics.yaml file, in the glean dashboard, as it's of type event it is displayed in the events ping.

@boek
Copy link
Contributor

boek commented May 29, 2019

@bsurd While it is under the metrics section, it's still a new top level declaration. We've started to move all events into their own namespace versus putting everything under events: and metrics:.

@spacesynth
Copy link

I'm using it! And please don't roast me for my offtopic, I didn't know where to ask, but it is growing on me, because of how much faster it is than my other QR readers.

What library is it based on?

@data-sync-user data-sync-user changed the title Telemetry for QR Scanner FNX2-17452 ⁃ Telemetry for QR Scanner Aug 4, 2020
@data-sync-user data-sync-user changed the title FNX2-17452 ⁃ Telemetry for QR Scanner FNX3-15864 ⁃ Telemetry for QR Scanner Aug 11, 2020
@data-sync-user data-sync-user changed the title FNX3-15864 ⁃ Telemetry for QR Scanner FNX-5287 ⁃ Telemetry for QR Scanner Aug 11, 2020
@data-sync-user data-sync-user changed the title FNX-5287 ⁃ Telemetry for QR Scanner Telemetry for QR Scanner May 19, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

10 participants