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

feat(mc): Add telemetry for Pocket #2911

Merged
merged 1 commit into from
Aug 9, 2017

Conversation

ncloudioj
Copy link
Member

This closes #2898. r? @k88hudson

@fmarier Could you take a look at the new pings defined in data_events.md?

@csadilek This is lite literally a direct port from the Test Pilot Pocket telemetry. Wanna take a quick look at it, please?

@@ -5,6 +5,7 @@ The Activity Stream system add-on sends various types of pings to the backend (H
- an `event` ping that records specific data about individual user interactions while interacting with Activity Stream
- a `performance` ping that records specific performance related events
- an `undesired` ping that records data about bad app states and missing data
- an `impresion_stats` ping that records data about Pocket impressions and user interactions
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo: missing 's'

@@ -264,3 +265,46 @@ perf: {
"visibility_event_rcvd_ts": 2,
}
```

## Pocket pings
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would be better to write Top Story pings or even more general Section/Card pings, but happy to fix it up later.

"tiles": [{"id": 10000, "pos": 0}],

// A 0-based index to record which tile in the "tiles" list that the user just interacted with.
"click|block|pocket": 0
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given that the "click" ping includes both the tiles ID and the client_id, could this measurement ever be mapped to a URL visit?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Technically yes. If that's a nope, we'll have to take out the client_id from this ping.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just to be clear, this id is currently generated by Pocket for each recommended story, and A-S team does not have access to the mapping of "id" -> "URL".

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Whether or not the URL-equivalent is attached to a user identifier, this is Category 3 data so it will need a full review.

I suggest reaching out to @bsmedberg since he also has context on the similar data collection that was done as part of the old tiles (Content Services).

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That makes sense. Thanks for pointing this out! @fmarier

@fmarier fmarier removed their assignment Jul 19, 2017
@ncloudioj
Copy link
Member Author

This PR is blocked by a data collection review tracked by this bug on bugzilla

@ncloudioj
Copy link
Member Author

@csadilek I've modified this PR to allow us to empty out user specific GUIDs in the impression ping. Could you take another look at it?

@ncloudioj ncloudioj force-pushed the gh2898-pocket-telemetry branch 2 times, most recently from a77f381 to 8fa19c1 Compare August 4, 2017 19:09
@coveralls
Copy link

Coverage Status

Coverage remained the same at 86.407% when pulling a77f381 on ncloudioj:gh2898-pocket-telemetry into 54a5392 on mozilla:master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 86.407% when pulling 8fa19c1 on ncloudioj:gh2898-pocket-telemetry into 54a5392 on mozilla:master.

@csadilek
Copy link
Collaborator

csadilek commented Aug 4, 2017

@ncloudioj lgtm! We still need to come up with a way to dedupe events or better to avoid sending duplicates, but that's for another day.

@ncloudioj
Copy link
Member Author

Hi @fmarier,

So all the user specific information has been emptied out from the events ping, and I've received the go-ahead call for that change on my end.

https://github.com/mozilla/activity-stream/pull/2911/files#diff-f9d20d6688eef2754298456e5d5b836b

Wanting to confirm with you here before I merge this patch. Does it make sense for you?

Thanks,

@fmarier
Copy link

fmarier commented Aug 8, 2017

Wanting to confirm with you here before I merge this patch. Does it make sense for you?

There is at least one more meeting on that topic before a conclusion is reached.

Rebecca Weiss is now handling this from a data stewardship point view.

@ncloudioj
Copy link
Member Author

Thanks for the update! @fmarier

Since this patch just added the telemetry APIs for Top Stories, but not sending anything out. I'll just merge it for now so that we can move forward.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 86.407% when pulling e2be8b1 on ncloudioj:gh2898-pocket-telemetry into e828511 on mozilla:master.

@ncloudioj ncloudioj removed the Blocked label Aug 9, 2017
@ncloudioj ncloudioj merged commit 6855f4f into mozilla:master Aug 9, 2017
@ncloudioj ncloudioj deleted the gh2898-pocket-telemetry branch August 9, 2017 15:25
@as-pine-proxy
Copy link
Collaborator

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

Successfully merging this pull request may close these issues.

Enable telemetry for Pocket in system addon
6 participants