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
1. Run the application, [see step 4 of Use variant feature flags](./howto-variant-feature-flags-javascript.md#run-the-application).
95
-
96
-
1. Create 10 different users and log into the application. As you log in with each user, you get a different message variant for some of them. ~50% of the time you get no message. 25% of the time you get the message "Hello!" and 25% of the time you get "I hope this makes your day!"
97
-
98
-
1. With some of the users click the **Like** button to trigger the telemetry event.
99
-
100
-
> [!div class="mx-imgBorder"]
101
-
>
102
-
103
-
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:
104
-
105
-
```kusto
106
-
// Step 1: Get distinct users and their Variant from FeatureEvaluation
>
94
+
1. Run the application, [see step 2 of Use variant feature flags](./howto-variant-feature-flags-python.md#build-and-run-the-app). You can simulate user activity on the application where some users are served different variants that they may or may not like.
158
95
159
-
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" event has 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.
96
+
## Next steps
160
97
161
-
For more information about the "FeatureEvaluation" event, go to the [Feature flag telemetry reference](./feature-flag-telemetry-reference.md)
98
+
- Now that you have set up your app and have some user activity on it, you can [review feature flag telemetry in the Azure Portal](./howto-telemetry.md#review-telemetry-for-feature-flag).
162
99
163
100
## Additional resources
164
101
165
102
- [Quote of the Day sample](https://github.com/Azure-Samples/quote-of-the-day-javascript)
166
-
167
-
## Next steps
168
-
169
-
For the full feature rundown of the JavaScript feature management library, refer to the following document.
- For the full feature rundown of the JavaScript feature management library you can refer to the [JavaScript Feature Management reference documentation](./feature-management-javascript-reference.md)
1. Run the application, [see step 2 of Use variant feature flags](./howto-variant-feature-flags-python.md#build-and-run-the-app).
109
-
110
-
1. Create 10 different users and log into the application. As you log in with each user, you get a different message variant for some of them. ~50% of the time you get no message. 25% of the time you get the message "Hello!" and 25% of the time you get "I hope this makes your day!".
111
-
112
-
1. With some of the users select the **Like** button to trigger the telemetry event.
113
-
114
-
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:
115
-
116
-
```kusto
117
-
// Step 1: Get distinct users and their Variant from FeatureEvaluation
1. Run the application, [see step 2 of Use variant feature flags](./howto-variant-feature-flags-python.md#build-and-run-the-app). You can simulate user activity on the application where some users are served different variants that they may or may not like.
165
109
166
-
```
167
-
168
-
> [!div class="mx-imgBorder"]
169
-
> 
170
-
171
-
You see one "FeatureEvaluation" for each time the quote page was loaded and one "Liked" event for each time the like button was clicked. The "FeatureEvaluation" event 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.
110
+
## Next steps
111
+
- Now that you have set up your app and have some user activity on it, you can [review feature flag telemetry in the Azure Portal](./howto-telemetry.md#review-telemetry-for-feature-flag).
172
112
173
113
## Additional resources
174
114
- [Flask Quote of the Day sample](https://github.com/Azure-Samples/quote-of-the-day-python)
Copy file name to clipboardExpand all lines: articles/azure-app-configuration/howto-telemetry.md
+114Lines changed: 114 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,3 +51,117 @@ These types of questions can be answered through the emission and analysis of fe
51
51
52
52
*[Python](./howto-telemetry-python.md)
53
53
*[JavaScript](./howto-telemetry-javascript.md)
54
+
55
+
## Review telemetry for feature flag
56
+
57
+
1. Navigate to the Application Insights blade in your Azure portal or monitoring dashboard. You'll see a graph displaying all events from your application. This provides an initial overview of activity patterns.
58
+
> [!div class="mx-imgBorder"]
59
+
> 
60
+
61
+
1. Use the time range selector to focus on specific periods. This helps identify trends or investigate particular timeframes of interest.
62
+
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
67
+
> [!div class="mx-imgBorder"]
68
+
> 
69
+
70
+
1. To access more detailed telemetry, click **"View details"** to open the telemetry tab.
71
+
> [!div class="mx-imgBorder"]
72
+
> 
73
+
74
+
In the telemetry tab, you can view:
75
+
76
+
-**Total events**: Total number of evaluation events emitted by your application
77
+
-**Unique users**: Number of distinct users who were targeted and for whom events were emitted.
78
+
79
+
80
+
81
+
**Verify variant assignments**
82
+
83
+
In order to show the distribution of users and number of evaluations across Simple, Long, and None variants, group the metrics by Variant. This will enable you see whether the configured allocations are working as expected, and that all expected variants are being served to users.
84
+
85
+
> [!div class="mx-imgBorder"]
86
+
> 
87
+
88
+
In this example, we see that the number of events for 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.
89
+
90
+
91
+
**Confirm overrides and behaviour based on flag state**
92
+
- Users may be assigned a variant for different reasons so you would want to ensure that your variant assignments are not only in the right proprtion, but also for the right reason. You can view this by grouping metrics by assignment reason. In this example, we will see that the only assignment reason is solely due to Percentile allocations.
93
+
94
+
> [!div class="mx-imgBorder"]
95
+
> 
96
+
97
+
- Disable the feature flag by going to the feature manager and toggling the feature flag off. Visit your feature flag telemetry tab and view Unique user count by Variant. You will see that all assignments for Long and Simple go to zero, and only the default variant (which is None in our case) is the only variant being assigned to users.
98
+
> [!div class="mx-imgBorder"]
99
+
> ![Screenshot of the Azure portal, view unique user count by variant in telemetry tab.]()
100
+
- Switch to group by unique user count by assignment reason.
101
+
Confirm from the graph that the Percentile allocations fall to zero and DefaultWhenDisabled is the only reason for which users are being assing variants.
102
+
- Other possible reasons include "Group Override" or "User Override" if configured.
103
+
> [!div class="mx-imgBorder"]
104
+
> ![Screenshot of the Azure portal, view unique user count by assignment reason in telemetry tab.]()
105
+
106
+
107
+
108
+
1. You can also access telemetry directly from the Feature Manager blade:
109
+
- Navigate to your Feature Manager
110
+
- Locate your feature flag in the displayed grid
111
+
- Click **"View events"** in the Telemetry column
112
+
> [!div class="mx-imgBorder"]
113
+
> 
114
+
115
+
## Analyze in Application Insights
116
+
117
+
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:
118
+
119
+
```kusto
120
+
// Step 1: Get distinct users and their Variant from FeatureEvaluation
164
+
165
+
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" event 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.
166
+
167
+
In this example, we can see that, even though there were roughly the same number of users getting the Long variant vs Simple, the Simple variant appears to be performing better by a margin of 20%.
0 commit comments