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/feature-flag-telemetry-reference.md
+7-8Lines changed: 7 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,9 +19,9 @@ In this document, you:
19
19
> - Learn what telemetry data is available using the Azure App Configuration provider libraries
20
20
> - Learn what telemetry data is available using the Feature Management libraries
21
21
22
-
## Viewing telemetry data
22
+
## Evaluation Event
23
23
24
-
With telemetry enabled no other properties are added to the feature flag besides the setting enabling telemetry. The use of one of the Azure App Configuration provider libraries along with the Feature Management libraries is required to start collecting telemetry data.
24
+
Telemetry for feature flags is available when using the Feature Management libraries.
25
25
26
26
### Basic fields
27
27
@@ -35,21 +35,20 @@ The feature management libraries provide the following properties to telemetry d
35
35
-**DefaultWhenEnabled**: The default variant of the feature flag when it's enabled.
36
36
-**Version**: The version of this schema.
37
37
-**VariantAssignmentPercentage**: Specifies the percentage of the user base the assigned variant is allocated for. This field is only present for percentile-based assignments.
38
-
-**AllocationID**: A unique identifier for the feature flag in its current state.
39
-
-**ETag**: The current ETag for the feature flag.
40
-
-**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>`.
41
38
42
-
The full schema can be found [here](https://github.com/microsoft/FeatureManagement/blob/main/Schema/FeatureEvaluationEvent/FeatureEvaluationEvent.v1.0.0.schema.json).
39
+
The full schema can be found in the [Feature Evaluation Event schema definition](https://github.com/microsoft/FeatureManagement/blob/main/Schema/FeatureEvaluationEvent/FeatureEvaluationEvent.v1.0.0.schema.json).
43
40
44
41
This data can then be sent to locations to be viewed, such as Azure Monitor. When using our provided connections to Azure Monitor, a **custom_event** is published with the following properties whenever a telemetry enabled feature flag is evaluated.
45
42
46
43
### App Configuration custom fields
47
44
48
45
When the Azure App Configuration provider libraries are used, additional properties are added to the telemetry data. These properties provide more context about the feature flag and its evaluation:
49
46
50
-
-**AllocationID**: A unique identifier for the feature flag in its current state.
47
+
-**AllocationID**: A unique identifier representing the state of the feature flag's allocation.
51
48
-**ETag**: The current ETag for the feature flag.
52
-
-**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>`.
49
+
-**FeatureFlagReference**: A reference to the feature flag in the format of `<your_store_endpoint>kv/<feature_flag_key>`. When a label is present, the reference includes it as a query parameter: `<your_store_endpoint>kv/<feature_flag_key>?label=<feature_flag_label>`.```
50
+
51
+
The full schema can be found in the [App Configuration Feature Evaluation Event schema definition](https://github.com/microsoft/FeatureManagement/blob/main/Schema/AppConfigurationFeatureEvaluationEvent/FeatureEvaluationEvent.v1.0.0.schema.json).
0 commit comments