Skip to content

Commit f26e75d

Browse files
committed
Updating bookmarks and strings.
1 parent 3ac2490 commit f26e75d

File tree

3 files changed

+5
-5
lines changed

3 files changed

+5
-5
lines changed

articles/azure-app-configuration/howto-telemetry-javascript.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -95,7 +95,7 @@ In this tutorial, you use telemetry in your Node.js application to track feature
9595
9696
## Next steps
9797
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).
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-the-feature-flag).
9999
100100
## Additional resources
101101

articles/azure-app-configuration/howto-telemetry-python.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -108,7 +108,7 @@ In this tutorial, you use telemetry in your Python application to track feature
108108
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.
109109
110110
## 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).
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-the-feature-flag).
112112
113113
## Additional resources
114114
- [Flask Quote of the Day sample](https://github.com/Azure-Samples/quote-of-the-day-python)

articles/azure-app-configuration/howto-telemetry.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,7 @@ These types of questions can be answered through the emission and analysis of fe
105105
> [!div class="mx-imgBorder"]
106106
> ![Screenshot of the Azure portal, view unique user count by variant in telemetry tab.](./media/howto-telemetry/unique-user-count-by-variant-disabled.png)
107107
108-
- Switch to group by unique user count by assignment reason.
108+
- Switch to view unique user count by assignment reason.
109109
Confirm from the graph that the Percentile allocations fall to zero and DefaultWhenDisabled is the only reason for which users are being assigned variants.
110110
- Other possible reasons include "Group Override" or "User Override" if configured.
111111
> [!div class="mx-imgBorder"]
@@ -165,6 +165,6 @@ Now that you have confirmed the feature flag allocations are working as expected
165165
> [!div class="mx-imgBorder"]
166166
> ![Screenshot of the Azure portal, view results of application insights analysis.](./media/howto-telemetry/application-insights-query-results.png)
167167
168-
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.
168+
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.
169169
170-
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 22%.
170+
In this example, we can see that, even though the number of users getting the Long variant vs Simple was roughly the same, the Simple variant appears to be performing better by a margin of 22%.

0 commit comments

Comments
 (0)