-
Notifications
You must be signed in to change notification settings - Fork 3
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
Feature/enhance telemetry #79
Conversation
Release 1.2.132
Release 1.2.135
Release 1.2.147
should we close this? @innovatechs @harrdou |
This is a new feature which is not yet integrated into the develop branch. We usually keep those features open until we do the merge. |
I recommend we close this PR if we're not actively working on it (i.e. has been prioritized by the team for the sprint). The feature/enhanceTelemetry branch is still there and we can re-open a new PR if needed. would that work? |
That works for me. @harrdou ? |
I've updated the PR description to better explain what this is about. This enhancement was mostly driven by client request for more information about their user' choices. With the new UX telemetry recently added to release 1.3.x, we now know track how many users choose to sign in with GCKey vs Interac, but not on a per-client basis and we don't distinguish between new and existing users. The number of users who have registered with more than one client can be determined now at the sector level by querying the database, but cannot be determined at the individual client level. Recording these events in Azure Monitor was just to make the data more accessible via Application Insights. |
@wmoussa-gc , I'm in agreement we can close the PR and keep the branch around. |
created an issue to track #142 |
Collects additional telemetry so that we can report on:
For new users:
For exiting users: