Whenever the AS panel is displayed we start a session with the name "activitystream.1". All events triggered while we show the panel will have this session name attached. Additionally we send a probe whenever the panel is shown/hidden.
- action = show.1
- method = panel
- extras = as_newtab
"New tab" panel hidden
- action = cancel.1
- method = panel
- extras = as_newtab
- action = loadurl.1
- method = listitem
- extras = as_top_sites
- action = loadurl.1
- method = listitem
- extras = as_highlights
- action = show.1
- method = contextmenu
- extras = as_top_sites
- action = show.1
- method = contextmenu
- extras = as_highlights
- action = share.1
- method = list
- extras = as_contextmenu
?
- action = action.1
- method = contextmenu
- extras = as_add_to_launcher
- action = loadurl.1
- method = contextmenu
- extras = as_new_tab
- action = loadurl.1
- method = contextmenu
- extras = as_private_tab
?
?
@grigoryk Yeah, from my point of view there are "two kinds of data" we are looking for:
For now all telemetry that landed was focused on (1) and copied the structure of our existing probes in other places. I agree that this is not sufficient for (2) and we want to track more detailed actions. My goal was to finish (1) and then talk to barbara and marina again so that they can start creating the reports in re:dash and let us know what additional data they are interested in; so that we have at least data parity with the desktop add-on.
Your format is looking good though. That's btw. the format and data the add-on collects:
https://github.com/mozilla/activity-stream/blob/master/data_events.md
I wonder if we can use the JSON functions of presotdb in re:dash or if we need to create our own spark jobs in order to use them. However it should be fairly easy to test that: Our telemetry for preferences already sends JSON formatted "extras".