Skip to content

Commit a747a22

Browse files
committed
acrolinx updates
1 parent fe16abd commit a747a22

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,8 @@ description: Learn how App Configuration allows for telemetry viewing for featur
55
ms.service: azure-app-configuration
66
author: mrm9084
77
ms.author: mametcal
8-
ms.topic: how-to
9-
ms.date: 10/31/2024
8+
ms.topic: reference
9+
ms.date: 11/06/2024
1010
---
1111

1212
# Tutorial: Feature flag telemetry reference (preview)
@@ -21,7 +21,7 @@ In this tutorial, you:
2121
2222
## Viewing telemetry data (Preview)
2323

24-
With telemetry (preview) enabled no other properties are added to the feature flag besides the setting enabling telemetry. The additional use of one of the Azure App Configuration provider libraries along with the Feature Management libraries is required to start collecting telemetry data.
24+
With telemetry (preview) 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.
2525

2626
### Azure App Configuration provider libraries
2727

@@ -36,7 +36,7 @@ The full schema can be found [here](https://github.com/microsoft/FeatureManageme
3636

3737
### Feature Management libraries
3838

39-
When feature flags with telemetry enabled are used with the Feature Management libraries in addition to the provider 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:
39+
When the Feature Management libraries and the provider libraries are used together, more properties are added to the telemetry data. 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 to Open Telemetry with the following properties whenever a telemetry enabled feature flag is evaluated:
4040

4141
- **Feature_Name**: The name of the feature flag.
4242
- **Enabled**: A boolean value indicating if the feature flag is enabled.

0 commit comments

Comments
 (0)