-
Notifications
You must be signed in to change notification settings - Fork 212
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
bug(settings): Backend events for login_reg and login_complete have gone missing #18059
base: main
Are you sure you want to change the base?
Conversation
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 don't see the entrypoint related changes. Did you forget to add some file to the commit?
@@ -118,23 +119,6 @@ export type AuthServerError = Error & { | |||
retryAfterLocalized?: string; | |||
}; | |||
|
|||
export const MetricsContextKeys = [ |
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.
@chenba, This collection was the issue. It didn't contain entrypoint.
*/ | ||
export class MetricsContext { | ||
deviceId?: string; | ||
entrypoint?: string; |
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.
@chenba entrypoint
is now a valid 'key' for Metricscontext
. With this addition, the query param and is now copied into the metrics context that is sent to the server.
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.
👍 Thanks
…one missing - Some back end events seemed to disappear - This is due to the entry point not being defined on the event - Fixes missing entrypoint glean data - Ensures entrypoint is sent in graphql requests if it is present in URL - Fixes typo in utm parameter. `utmContext` should have been `utmContent`. - Puts the `MetricContext` model in a shared place to reduce the chance this happens again.
Because
This pull request
utmContext
should have beenutmContent
.MetricContext
model in a shared place to reduce the chance this happens again.Issue that this pull request solves
Closes: # (issue number)
Checklist
Put an
x
in the boxes that apply