Enhance Application Insights tracking with user-specific properties and simplified event naming #618
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary & Motivation
Update Application Insights tracking for custom events by adding user-specific properties such as
UserId
,TenantId
,Local
,UserRole
, andIsAuthenticated
. These properties are prefixed withuser_
(e.g.,user_Local
,user_IsAuthenticated
) by convention, ensuring consistency and enhancing the clarity of user-related data in telemetry.The creation of telemetry events has also been simplified to reduce errors. Event names are now derived using
GetType().Name
instead ofnameof(EventName)
, avoiding issues from copy-pasting, such as whenUserUpdated
events were incorrectly named asUserCreated
.Additionally, telemetry tracking is now updated to collect
UserId
andTenantId
specifically in unauthenticated login flows and admin role changes, ensuring precise event data collection for critical user actions.Checklist