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
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ In this tutorial, you:
30
30
31
31
1. Open your App Configuration store in the Azure portal.
32
32
1. In the **Operations** section, select the **Feature manager** page.
33
-
1. When viewing the list of feature flags, you should see a column labeled **Telemetry** (preview), it should be currently show as **Disabled**. Right click on the feature flag you want to enable telemetry for and select **Edit**.
33
+
1. When viewing the list of feature flags, you should see a column labeled **Telemetry** (preview), it should show as **Disabled**. Right click on the feature flag you want to enable telemetry for and select **Edit**.
34
34
1. In the new view, select the **Telemetry** tab.
35
35
1. Select the **Enable Telemetry** checkbox and then the **Review + update** button at the bottom of the page.
36
36
1. On the **Review + update** page, select the **Update** button.
@@ -39,29 +39,29 @@ In this tutorial, you:
39
39
40
40
With telemetry (preview) enabled no other properties are added to the feature flag besides the setting enabling telemetry. Use of an Azure App Configuration provider library that supports telemetry is required to start collecting telemetry data.
41
41
42
-
When, telemetry is enabled the Azure App Configuration provider libraries add more properties to the feature flags when they are retrieved. A new object is added to the **telemetry** section of the feature flag called **metadata**. The **metadata** object contains the following properties:
42
+
When telemetry is enabled, the Azure App Configuration provider libraries add more properties to the feature flags when they're retrieved. A new object is added to the **telemetry** section of the feature flag called **metadata**. The **metadata** object contains the following properties:
43
43
44
-
-**AllocationID**: A unique identifier for the feature flag in it's current state.
44
+
-**AllocationID**: A unique identifier for the feature flag in its current state.
45
45
-**ETag**: The current ETag for the feature flag.
46
46
-**FeatureFlagReference**: A reference to the feature flag in the format of **<your-store-endpoint>kv/<feature_flag_key>**, it also includes the label if one is present, **<your-store-endpoint>kv/<feature_flag_key>?label=<feature_flag_label>**
47
47
-**FeatureFlagId**: A unique identifier for the feature flag.
48
48
49
49
The full schema can be found [here](https://github.com/microsoft/FeatureManagement/tree/main/Schema/FeatureEvaluationEvent/FeatureEvaluationEventWithAzureAppConfiguration.v1.0.0.schema.json).
50
50
51
-
When, feature flags with telemetry enabled are used with the Feature Management libraries more properties are added to the telemetry data and be sent to location to be viewed, such as Azure Monitor. When using our provided connections to Azure Monitor are used a **custom_event** is be published to Open Telemetry with the following properties whenever a telemetry enabled feature flag is evaluated:
51
+
When feature flags with telemetry enabled are used with the Feature Management libraries, more properties are added to the telemetry data and be sent to location to be viewed, such as Azure Monitor. When using our provided connections to Azure Monitor a **custom_event** is published to Open Telemetry with the following properties whenever a telemetry enabled feature flag is evaluated:
52
52
53
53
-**Feature_Name**: The name of the feature flag.
54
54
-**Enabled**: A boolean value indicating if the feature flag is enabled.
55
55
-**Version**: The version of this schema.
56
56
-**Reason**: The reason the feature flag was enabled or disabled.
57
57
-**Variant**: The variant that was selected for the feature flag.
58
58
-**VariantAssignmentPercentage**: If a variant wasn't targeted specifically at the user, or one of the user's groups, this number is the Percentage chance of the user being assigned to the variant.
59
-
-**DefaultWhenEnabled**: The default variant of the feature flag when it is enabled.
60
-
-**AllocationID**: A unique identifier for the feature flag in it's current state.
59
+
-**DefaultWhenEnabled**: The default variant of the feature flag when it's enabled.
60
+
-**AllocationID**: A unique identifier for the feature flag in its current state.
61
61
-**ETag**: The current ETag for the feature flag.
62
-
-**FeatureFlagReference**: A reference to the feature flag in the format of **<your-store-endpoint>kv/<feature_flag_key>**, it will also include the label if one is present, **<your-store-endpoint>kv/<feature_flag_key>?label=<feature_flag_label>**
62
+
-**FeatureFlagReference**: A reference to the feature flag in the format of **<your-store-endpoint>kv/<feature_flag_key>**, it also includes the label if one is present, **<your-store-endpoint>kv/<feature_flag_key>?label=<feature_flag_label>**
63
63
-**FeatureFlagId**: A unique identifier for the feature flag.
64
-
-**TargetingId**: The id of the user that was assigned to the variant.
64
+
-**TargetingId**: The ID of the user that was assigned to the variant.
65
65
66
66
The full schema can be found [here](https://github.com/microsoft/FeatureManagement/blob/main/Schema/FeatureEvaluationEvent/FeatureEvaluationEvent.v1.0.0.schema.json).
0 commit comments