Closed Bug 1656568 Opened 4 years ago Closed 4 years ago

Update nimbus events to set event_object="nimbus_experiment"

Categories

(Firefox :: Nimbus Desktop Client, enhancement, P1)

enhancement
Points:
2

Tracking

()

RESOLVED FIXED
88 Branch
Iteration:
81.2 - Aug 10 - Aug 23
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.

Let's take a look at:

  • if this should use the shared codepath / helpers that Normandy uses
  • if we should use a different category than normandy

Tim, any opinions on how hard it would be to support a different category type for nimbus?

Flags: needinfo?(tdsmith)
Assignee: nobody → mcooper
Iteration: --- → 81.2 - Aug 10 - Aug 23
Priority: -- → P1

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.

Flags: needinfo?(tdsmith)

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.

Component: Messaging System → Nimbus Desktop Client
Attachment #9176422 - Attachment is obsolete: true
Summary: Audit enrollment events for Xman → Update nimbus events to set event_object="nimbus_experiment"

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: mcooper → khudson
Blocks: 1694408
No longer blocks: x-man
Points: --- → 2
Pushed by khudson@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/24b91deee352 Use a specific event object for nimbus events r=andreio
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 88 Branch
Regressions: 1699761
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: