Merge pull request #276744 from MicrosoftDocs/main

5/30/2024 AM Publish

Author: Taojunshen

articles/api-management/azure-openai-emit-token-metric-policy.md

@@ -66,7 +66,7 @@ The `azure-openai-emit-token-metric` policy sends metrics to Application Insight
 * Product ID
 * User ID
 * Subscription ID
-* Location ID
+* Location
 * Gateway ID
 
 ## Usage

articles/api-management/emit-metric-policy.md

@@ -60,7 +60,7 @@ The `emit-metric` policy sends custom metrics in the specified format to Applica
 * Product ID
 * User ID
 * Subscription ID
-* Location ID
+* Location
 * Gateway ID
 
 ## Usage

articles/azure-app-configuration/concept-config-file.md

@@ -4,8 +4,8 @@ description: Tooling support for using configuration files with Azure App Config
 author: zhenlan
 ms.author: zhenlwa
 ms.service: azure-app-configuration
-ms.topic: conceptual
-ms.date: 10/28/2022
+ms.topic: concept
+ms.date: 05/30/2024
 ---
 
 # Azure App Configuration support for configuration files
@@ -102,9 +102,11 @@ The following example is a file based upon the KVSet file content profile, named
 
 > [!TIP]
 > If you followed the example in the previous section and have the data in your App Configuration store, you can export it to a file using the CLI command:
+
 > ```azurecli-interactive
 > az appconfig kv export --profile appconfig/kvset --label * --name <your store name> --destination file --path appconfigdata.json --format json 
 > ```
+
 > After the file is exported, update the `Beta` feature flag `enabled` property to `true` and change the `Logging:LogLevel:Default` to `Debug`.
 
 Run the following CLI command with the parameter "**--profile appconfig/kvset**" to import the file to your App Configuration store. You don't need to specify any data transformation rules such as separator, label, or content type like you did in the default file content profile section because all information is already in the file.

articles/azure-app-configuration/quickstart-bicep.md

@@ -4,7 +4,7 @@ titleSuffix: Azure App Configuration
 description: Learn how to create an Azure App Configuration store using Bicep.
 author: maud-lv
 ms.author: malev
-ms.date: 05/06/2022
+ms.date: 05/30/2024
 ms.service: azure-app-configuration
 ms.topic: quickstart
 ms.custom: subject-armqs, mode-arm, devx-track-bicep

articles/azure-monitor/app/api-custom-events-metrics.md

@@ -678,7 +678,8 @@ telemetry.flush();
 The function is asynchronous for the [server telemetry channel](https://www.nuget.org/packages/Microsoft.ApplicationInsights.WindowsServer.TelemetryChannel/).
 
 > [!NOTE]
-> The Java and JavaScript SDKs automatically flush on application shutdown.
+> - The Java and JavaScript SDKs automatically flush on application shutdown.
+> - **Review Autoflush configuration**: [Enabling autoflush](https://learn.microsoft.com/dotnet/api/system.diagnostics.trace.autoflush) in your `web.config` file can lead to performance degradation in .NET applications instrumented with Application Insights. With autoflush enabled, every invocation of `System.Diagnostics.Trace.Trace*` methods results in individual telemetry items being sent as separate distinct web requests to the ingestion service. This can potentially cause network and storage exhaustion on your web servers. For enhanced performance, it’s recommended to disable autoflush and also, utilize the [ServerTelemetryChannel](https://learn.microsoft.com/azure/azure-monitor/app/telemetry-channels#built-in-telemetry-channels), designed for a more effective telemetry data transmission.
 
 ## Authenticated users
 

articles/azure-monitor/app/opentelemetry-overview.md

@@ -24,7 +24,7 @@ There are two methods to instrument your application:
 > [!TIP]
 > Currently, [Microsoft Entra authentication](azure-ad-authentication.md) is not available with autoinstrumentation. If you require Microsoft Entra auth, you'll need to use manual instrumentation.
 
-**Manual instrumentation** is coding against the Application Insights or OpenTelemetry API. In the context of a user, it typically refers to installing a language-specific SDK in an application. There are two options for manual instrumentation:
+**Manual instrumentation** is coding against the Application Insights or OpenTelemetry API. In the context of a user, it typically refers to installing a language-specific SDK in an application. This means that you have to manage the updates to the latest package version by yourself. You can use this option if you need to make custom dependency calls or API calls that are not captured by default with autoinstrumentation. There are two options for manual instrumentation:
 
 - [Application Insights SDKs](asp-net-core.md)
 - [Azure Monitor OpenTelemetry Distros](opentelemetry-enable.md).

articles/azure-monitor/autoscale/autoscale-common-scale-patterns.md

@@ -3,7 +3,7 @@ title: Overview of common autoscale patterns
 description: Learn some of the common patterns to use with autoscale for your resource in Azure.
 author: EdB-MSFT
 ms.topic: conceptual
-ms.date: 11/17/2022
+ms.date: 05/31/2024
 ms.subservice: autoscale
 ms.author: edbaynash
 ms.reviewer: akkumari

articles/azure-monitor/containers/prometheus-authorization-proxy.md

@@ -5,7 +5,7 @@ ms.topic: how-to
 ms.custom: devx-track-azurecli
 author: EdB-MSFT
 ms.author: edbaynash
-ms.date: 07/10/2022
+ms.date: 05/31/2024
 ---
 
 # Microsoft Entra authorization proxy 

articles/azure-monitor/essentials/azure-monitor-workspace-manage.md

@@ -6,7 +6,7 @@ ms.author: edbaynash
 ms.reviewer: poojaa
 ms.topic: conceptual
 ms.custom: devx-track-azurecli
-ms.date: 03/28/2023
+ms.date: 05/31/2024
 ---
 
 # Manage an Azure Monitor workspace

articles/azure-monitor/essentials/azure-monitor-workspace-overview.md

@@ -5,7 +5,7 @@ author: EdB-MSFT
 ms.author: edbaynash 
 ms.reviewer: poojaa
 ms.topic: conceptual
-ms.date: 01/22/2023
+ms.date: 05/31/2024
 ---
 
 # Azure Monitor workspace