Skip to content

Commit 4a736a6

Browse files
committed
review comments
1 parent b8aa036 commit 4a736a6

File tree

1 file changed

+7
-8
lines changed

1 file changed

+7
-8
lines changed

articles/azure-app-configuration/feature-flag-telemetry-reference.md

Lines changed: 7 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -19,9 +19,9 @@ In this document, you:
1919
> - Learn what telemetry data is available using the Azure App Configuration provider libraries
2020
> - Learn what telemetry data is available using the Feature Management libraries
2121
22-
## Viewing telemetry data
22+
## Evaluation Event
2323

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.
2525

2626
### Basic fields
2727

@@ -35,21 +35,20 @@ The feature management libraries provide the following properties to telemetry d
3535
- **DefaultWhenEnabled**: The default variant of the feature flag when it's enabled.
3636
- **Version**: The version of this schema.
3737
- **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>`.
4138

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).
4340

4441
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.
4542

4643
### App Configuration custom fields
4744

4845
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:
4946

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.
5148
- **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).
5352

5453
## Next steps
5554

0 commit comments

Comments
 (0)