-
Notifications
You must be signed in to change notification settings - Fork 4k
Add MetricsEvent proto & Fivetran infrastructure
#9695
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
lukasmasuch
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍 Added one general question related tot the event structure
| string label = 22; | ||
|
|
||
|
|
||
| // Page Profile Event fields: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to keep this a flat structure? If nesting is fine we could potentially use an oneof here to have a better separation between the different event types, e.g.:
oneof metadata {
PageProfile page_profile = 1;
MenuClick menu_click = 2;In that case, we could potentially also reuse the existing page profile message by moving all the frontend added fields into it as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had same thought, but then DS confirmed during testing its much easier to work with in flat structure (Fivetran does not auto-flatten the same way Segment did) so they strongly preferred this version
**Metrics Migration Part 2:** This PR adds a `MetricsEvent` proto for a single source of truth for event fields, as well as the infrastructure necessary to send event data to the testing Fivetran webhook in parallel with Segment. This includes building the `anonymousId` & `context` data fields for FW that we received by default from Segment.
Describe your changes
Metrics Migration Part 2: This PR adds a
MetricsEventproto for a single source of truth for event fields, as well as the infrastructure necessary to send event data to the testing Fivetran webhook in parallel with Segment. This includes building theanonymousId&contextdata fields for FW that we received by default from Segment.Testing Plan
See demo app here & metrics comparison app here