You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-app-configuration/howto-telemetry.md
+77-76Lines changed: 77 additions & 76 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,55 +61,55 @@ These types of questions can be answered through the emission and analysis of fe
61
61
1. Use the time range selector to focus on specific periods to identify trends or investigate particular timeframes of interest.
62
62
63
63
1. Filter by feature Flag
64
-
- Click on the dropdown menu above the event graph
65
-
- Under **Feature flags with events** select your feature flag
66
-
- The graph will now display only events related to the feature flag's evaluations
64
+
1. Click on the dropdown menu above the event graph
65
+
1. Under **Feature flags with events** select your feature flag
66
+
1. The graph will now display only events related to the feature flag's evaluations
67
67
> [!div class="mx-imgBorder"]
68
68
> 
69
69
70
70
1. To access more detailed telemetry, click **View details** to open the telemetry tab.
71
71
> [!div class="mx-imgBorder"]
72
72
> 
73
73
74
-
You can also access this tab by going to the **Feature manager** and clicking **View events** in the telemetry column for the feature flag of interest.
75
-
> [!div class="mx-imgBorder"]
76
-
> 
74
+
> [!NOTE]
75
+
> You can also access this tab by going to the **Feature manager** and clicking **View events** in the telemetry column for the feature flag of interest.
76
+
> 
77
77
78
78
79
-
In the telemetry tab, you can view:
79
+
### Verify variant assignments
80
80
81
-
-**Total events**: Total number of evaluation events emitted by your application
82
-
-**Unique users**: Number of distinct users who were targeted and for whom events were emitted.
83
-
81
+
In the telemetry tab, you can view:
84
82
83
+
-**Total events**: Total number of evaluation events emitted by your application
84
+
-**Unique users**: Number of distinct users who were targeted and for whom events were emitted.
85
85
86
-
**Verify variant assignments**
87
-
88
-
In order to show the distribution of users and number of evaluations across Simple, Long, and None variants, group the metrics by Variant. This grouping enables you to see whether the configured allocations are working as expected, and that all expected variants are being served to users.
86
+
In order to show the distribution of users and number of evaluations across Simple, Long, and None variants, group the metrics by Variant. This grouping enables you to see whether the configured allocations are working as expected, and that all expected variants are being served to users.
89
87
90
-
> [!div class="mx-imgBorder"]
91
-
> 
88
+
> [!div class="mx-imgBorder"]
89
+
> 
92
90
93
-
In this example, we see that the number of users assigned the "None" variant is almost twice that of the "Simple" and "Long" variants given the configured 50-25-25 percentile split between "None", "Simple" and "Long" respectively.
91
+
In this example, we see that the number of users assigned the "None" variant is almost twice that of the "Simple" and "Long" variants given the configured 50-25-25 percentile split between "None", "Simple" and "Long" respectively.
94
92
95
93
96
-
**Confirm overrides and behavior based on flag state**
97
-
- Users may receive a variant for different reasons. You want to ensure that your variant assignments aren't only in the right proportion, but also for the right reason. You can group metrics by assignment reason. In this example, we see that the only assignment reason is solely due to Percentile allocations.
94
+
### Confirm overrides and behavior based on flag state
98
95
99
-
> [!div class="mx-imgBorder"]
100
-
> 
96
+
Users may receive a variant for different reasons. You want to ensure that your variant assignments aren't only in the right proportion, but also for the right reason. You can group metrics by assignment reason. In this example, we see that the only assignment reason is solely due to Percentile allocations.
101
97
102
-
- Disable the feature flag by going to the feature manager and toggling the feature flag "Enable" switch.
103
-
- In the telemetry column, click **View events** to go to telemetry tab in read-only mode.
104
-
- View Unique user count by Variant. You should see that all assignments for Long and Simple go to zero. Only the None variant, which is the default in our case, is assigned to users.
105
-
> [!div class="mx-imgBorder"]
106
-
> 
98
+
> [!div class="mx-imgBorder"]
99
+
> 
107
100
108
-
- Switch to view unique user count by assignment reason.
109
-
Confirm from the graph that the Percentile allocations fall to zero and DefaultWhenDisabled is the only reason for which users are being assigned variants.
110
-
- Other possible reasons include "Group Override" or "User Override" if configured.
111
-
> [!div class="mx-imgBorder"]
112
-
> 
101
+
- Disable the feature flag by going to the feature manager and toggling the feature flag "Enable" switch.
102
+
- In the telemetry column, click **View events** to go to telemetry tab in read-only mode.
103
+
- View Unique user count by Variant. You should see that all assignments for Long and Simple go to zero. Only the None variant, which is the default in our case, is assigned to users.
104
+
> [!div class="mx-imgBorder"]
105
+
> 
106
+
107
+
- Switch to view unique user count by assignment reason.
108
+
Confirm from the graph that the Percentile allocations fall to zero and DefaultWhenDisabled is the only reason for which users are being assigned variants.
109
+
110
+
Other possible reasons include "Group Override" or "User Override" if configured.
111
+
> [!div class="mx-imgBorder"]
112
+
> 
113
113
114
114
115
115
## Analyze in Application Insights
@@ -118,53 +118,54 @@ Now that you have confirmed the feature flag allocations are working as expected
118
118
119
119
1. Open your Application Insights resource in the Azure portal and select **Logs** under **Monitoring**. In the query window, run the following query to see the telemetry events:
120
120
121
-
```kusto
122
-
// Step 1: Get distinct users and their Variant from FeatureEvaluation
123
-
let evaluated_users =
124
-
customEvents
125
-
| where name == "FeatureEvaluation"
126
-
| where tostring(customDimensions.FeatureFlagReference) == "https://<store-endpoint>/kv/.appconfig.featureflag/<feature-flag-name>?label=<feature-flag-label>"
> 
168
169
169
170
You see one "FeatureEvaluation" event for each time the quote page was loaded and one "Liked" event for each time the like button was clicked. The "FeatureEvaluation" events have a custom property called `FeatureName` with the name of the feature flag that was evaluated. Both events have a custom property called `TargetingId` with the name of the user that liked the quote.
0 commit comments