Land urlbar.picked.* keyed scalars into `clients_daily`
Categories
(Data Platform and Tools :: General, task)
Tracking
(Not tracked)
People
(Reporter: teon, Unassigned)
Details
Attachments
(1 file)
I would like to have the urlbar.picked.* keyed scalar accessible in clients_daily
so that they are easier to access in redash. These probes exist in the main
table but we did not have these probes queued to be added to clients_daily
.
We need these scalars to explore the relationship of the selection based on the index and the a category/type. This will inform upcoming experiments design and redesign of the AwesomeBar.
Also, if it works for these to be written directly to a separate table, I would be for that as well. Ideally, I would like to have a product-specific view of the AwesomeBar, but we need the intermediary to be clients_daily
, I can work to build the view from it.
Happy to give my details about this.
Probes
urlbar_picked_autofill
urlbar_picked_bookmark
urlbar_picked_dynamic
urlbar_picked_extension
urlbar_picked_formhistory
urlbar_picked_history
urlbar_picked_keyword
urlbar_picked_remotetab
urlbar_picked_searchengine
urlbar_picked_searchsuggestion
urlbar_picked_switchtab
urlbar_picked_tabtosearch
urlbar_picked_tip
urlbar_picked_topsite
urlbar_picked_unknown
urlbar_picked_visiturl
Comment 1•3 years ago
|
||
Can you provide more detail about how these would need to be aggregated? Do we need sum per key? What are the possible key values?
Comment 2•3 years ago
|
||
Looking more into existing practice in clients_daily, I see that we have existing keyed scalars that we aggregate by summing per key and presenting as an array of key/value pairs. Should be straightforward.
Comment 3•3 years ago
|
||
Comment 4•3 years ago
|
||
This is now deployed and clients_daily backfill is complete for 2021-04-14 to present. clients_last_seen backfill will run overnight.
Assignee | ||
Updated•2 years ago
|
Description
•