Update nimbus events to set event_object="nimbus_experiment"
Categories
(Firefox :: Nimbus Desktop Client, enhancement, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox88 | --- | fixed |
People
(Reporter: k88hudson, Assigned: k88hudson)
References
Details
Attachments
(1 file, 1 obsolete file)
Let's audit all the fields for how we send enrollment telemetry for Nimbus experiments, if we want to send something other than normandy
, etc.
Assignee | ||
Comment 1•4 years ago
|
||
Let's take a look at:
- if this should use the shared codepath / helpers that Normandy uses
- if we should use a different
category
thannormandy
Tim, any opinions on how hard it would be to support a different category
type for nimbus?
Assignee | ||
Updated•4 years ago
|
Comment 2•4 years ago
|
||
If the enrolment events have the same format, this should be as easy as replacing = 'normandy'
with IN ('normandy', 'nimbus')
in mozanalysis, Jetstream, and the aggregates table powering Grafana. If the formats are a little different, we can probably publish a view that smooths over the differences.
So this doesn't seem like a catastrophic amount of work. We'd have to explain to data scientists why they might have to look in a second place for data.
We could add a source: <normandy|nimbus>
extra to the event if we don't want to change the name and feel it's important to disambiguate the origin.
Comment 3•4 years ago
|
||
I expect that overtime Nimbus will have it's own unique needs for telemetry, and trying to align Normandy and Nimbus long term will produce a rather confused schema. I think we should fork the Normandy schema, and keep just the parts relevant to Nimbus. Then we don't have to worry about cross-compatibility. I'll make these code changes soon.
Assignee | ||
Updated•4 years ago
|
Comment 4•4 years ago
|
||
Updated•4 years ago
|
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 5•4 years ago
|
||
After discussing this with mythmon we're going to go with with updating the event object v.s. changing the category for now. All nimbus-related events should will a category of nimbus_experiment
(which also means updating the exposure event)
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 6•4 years ago
|
||
Comment 8•4 years ago
|
||
bugherder |
Description
•