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

[Meta] Integrate Glean SDK (Event Ping) #923

Closed
bbinto opened this issue Mar 8, 2019 · 4 comments
Closed

[Meta] Integrate Glean SDK (Event Ping) #923

bbinto opened this issue Mar 8, 2019 · 4 comments

Comments

@bbinto
Copy link
Contributor

bbinto commented Mar 8, 2019

Follow-up to #105

This Epic is about enabling and hooking up Fenix with the Glean SDK event pings

Dependencies

┆Issue is synchronized with this Jira Task

@bbinto bbinto added this to the MVP Metas milestone Mar 8, 2019
@bbinto bbinto added the Epic label Mar 8, 2019
@bbinto bbinto added the must label Mar 18, 2019
@bbinto
Copy link
Contributor Author

bbinto commented Mar 20, 2019

@st3fan could you please help break this into tasks/user stories? I'm not quite sure about the work that has to happen for the SDK integration piece. Thanks

@boek
Copy link
Contributor

boek commented Mar 20, 2019

@bbinto I think I might have handled most of the work for this in #1067

Though I'm not sure what is the best way to test it.

@bbinto
Copy link
Contributor Author

bbinto commented Mar 20, 2019

@georgf - can @boek just send and hit a button and you wait on the other end to see if it came through to you ;) Clearly, I'm simplying this ;)

@georgf
Copy link

georgf commented Mar 21, 2019

@boek I think the best way right now is to use the debugging commands here.

You would first:

  • enable logging of pings: adb shell am start ... --ez logPings true
  • then trigger the event ping: adb shell am start ... --es sendPing events
    You should then see the JSON ping dumped to logcat and could check that it contains the events you recorded.

Let us know if that doesn't work out for you.

By April 15 we will have an easier testing solution in place: a web interface to see your data come in in soft realtime.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants