changed files by pdets auto publish service, publishid[3b68a842-b5b4-4ed0-8c36-ca7de991ef03] and do [publish].

wwlpublish · web-flow · commit 74f064debe09 · 2025-06-30T10:22:56.000+08:00
diff --git a/learn-pr/azure/monitor-app-performance/1-introduction.yml b/learn-pr/azure/monitor-app-performance/1-introduction.yml
@@ -1,15 +1,17 @@
-### YamlMime:ModuleUnit
-uid: learn.wwl.monitor-app-performance.introduction
-title: Introduction
-metadata:
-  title: Introduction
-  description: "Introduction"
-  ms.date: 07/18/2024
-  author: wwlpublish
-  ms.author: jeffko
-  ms.topic: unit
-  ms.custom:
-  - N/A
-durationInMinutes: 3
-content: |
-  [!include[](includes/1-introduction.md)]
+### YamlMime:ModuleUnit
+uid: learn.wwl.monitor-app-performance.introduction
+title: Introduction
+metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
+  title: Introduction
+  description: "Introduction"
+  ms.date: 06/30/2025
+  author: wwlpublish
+  ms.author: jeffko
+  ms.topic: unit
+  ms.custom:
+  - N/A
+durationInMinutes: 3
+content: |
+  [!include[](includes/1-introduction.md)]
diff --git a/learn-pr/azure/monitor-app-performance/2-application-insights-overview.yml b/learn-pr/azure/monitor-app-performance/2-application-insights-overview.yml
@@ -1,15 +1,17 @@
-### YamlMime:ModuleUnit
-uid: learn.wwl.monitor-app-performance.explore-application-insights
-title: Explore Application Insights
-metadata:
-  title: Explore Application Insights
-  description: "Explore Application Insights"
-  ms.date: 07/18/2024
-  author: wwlpublish
-  ms.author: jeffko
-  ms.topic: unit
-  ms.custom:
-  - N/A
-durationInMinutes: 3
-content: |
-  [!include[](includes/2-application-insights-overview.md)]
+### YamlMime:ModuleUnit
+uid: learn.wwl.monitor-app-performance.explore-application-insights
+title: Explore Application Insights
+metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
+  title: Explore Application Insights
+  description: "Explore Application Insights"
+  ms.date: 06/30/2025
+  author: wwlpublish
+  ms.author: jeffko
+  ms.topic: unit
+  ms.custom:
+  - N/A
+durationInMinutes: 3
+content: |
+  [!include[](includes/2-application-insights-overview.md)]
diff --git a/learn-pr/azure/monitor-app-performance/3-logs-based-metrics.yml b/learn-pr/azure/monitor-app-performance/3-logs-based-metrics.yml
@@ -1,15 +1,17 @@
-### YamlMime:ModuleUnit
-uid: learn.wwl.monitor-app-performance.discover-log-based-metrics
-title: Discover log-based metrics
-metadata:
-  title: Discover log-based metrics
-  description: "Discover log-based metrics"
-  ms.date: 07/18/2024
-  author: wwlpublish
-  ms.author: jeffko
-  ms.topic: unit
-  ms.custom:
-  - N/A
-durationInMinutes: 3
-content: |
-  [!include[](includes/3-logs-based-metrics.md)]
+### YamlMime:ModuleUnit
+uid: learn.wwl.monitor-app-performance.discover-log-based-metrics
+title: Discover log-based metrics
+metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
+  title: Discover log-based metrics
+  description: "Discover log-based metrics"
+  ms.date: 06/30/2025
+  author: wwlpublish
+  ms.author: jeffko
+  ms.topic: unit
+  ms.custom:
+  - N/A
+durationInMinutes: 3
+content: |
+  [!include[](includes/3-logs-based-metrics.md)]
diff --git a/learn-pr/azure/monitor-app-performance/4-app-instrumentation.yml b/learn-pr/azure/monitor-app-performance/4-app-instrumentation.yml
@@ -1,15 +1,17 @@
-### YamlMime:ModuleUnit
-uid: learn.wwl.monitor-app-performance.instrument-app-for-monitoring
-title: Instrument an app for monitoring
-metadata:
-  title: Instrument an app for monitoring
-  description: "Instrument an app for monitoring"
-  ms.date: 07/18/2024
-  author: wwlpublish
-  ms.author: jeffko
-  ms.topic: unit
-  ms.custom:
-  - N/A
-durationInMinutes: 3
-content: |
-  [!include[](includes/4-app-instrumentation.md)]
+### YamlMime:ModuleUnit
+uid: learn.wwl.monitor-app-performance.instrument-app-for-monitoring
+title: Instrument an app for monitoring
+metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
+  title: Instrument an app for monitoring
+  description: "Instrument an app for monitoring"
+  ms.date: 06/30/2025
+  author: wwlpublish
+  ms.author: jeffko
+  ms.topic: unit
+  ms.custom:
+  - N/A
+durationInMinutes: 3
+content: |
+  [!include[](includes/4-app-instrumentation.md)]
diff --git a/learn-pr/azure/monitor-app-performance/5-availability-tests.yml b/learn-pr/azure/monitor-app-performance/5-availability-tests.yml
@@ -1,15 +1,17 @@
-### YamlMime:ModuleUnit
-uid: learn.wwl.monitor-app-performance.select-availability-test
-title: Select an availability test
-metadata:
-  title: Select an availability test
-  description: "Select an availability test"
-  ms.date: 07/18/2024
-  author: wwlpublish
-  ms.author: jeffko
-  ms.topic: unit
-  ms.custom:
-  - N/A
-durationInMinutes: 3
-content: |
-  [!include[](includes/5-availability-tests.md)]
+### YamlMime:ModuleUnit
+uid: learn.wwl.monitor-app-performance.select-availability-test
+title: Select an availability test
+metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
+  title: Select an availability test
+  description: "Select an availability test"
+  ms.date: 06/30/2025
+  author: wwlpublish
+  ms.author: jeffko
+  ms.topic: unit
+  ms.custom:
+  - N/A
+durationInMinutes: 3
+content: |
+  [!include[](includes/5-availability-tests.md)]
diff --git a/learn-pr/azure/monitor-app-performance/6-application-map.yml b/learn-pr/azure/monitor-app-performance/6-application-map.yml
@@ -1,15 +1,17 @@
-### YamlMime:ModuleUnit
-uid: learn.wwl.monitor-app-performance.troubleshoot-by-using-application-map
-title: Troubleshoot app performance by using Application Map
-metadata:
-  title: Troubleshoot app performance by using Application Map
-  description: "Troubleshoot app performance by using Application Map"
-  ms.date: 07/18/2024
-  author: wwlpublish
-  ms.author: jeffko
-  ms.topic: unit
-  ms.custom:
-  - N/A
-durationInMinutes: 3
-content: |
-  [!include[](includes/6-application-map.md)]
+### YamlMime:ModuleUnit
+uid: learn.wwl.monitor-app-performance.troubleshoot-by-using-application-map
+title: Troubleshoot app performance by using Application Map
+metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
+  title: Troubleshoot app performance by using Application Map
+  description: "Troubleshoot app performance by using Application Map"
+  ms.date: 06/30/2025
+  author: wwlpublish
+  ms.author: jeffko
+  ms.topic: unit
+  ms.custom:
+  - N/A
+durationInMinutes: 3
+content: |
+  [!include[](includes/6-application-map.md)]
diff --git a/learn-pr/azure/monitor-app-performance/6a-monitor-application-instrumentation.yml b/learn-pr/azure/monitor-app-performance/6a-monitor-application-instrumentation.yml
@@ -0,0 +1,17 @@
+### YamlMime:ModuleUnit
+uid: learn.wwl.monitor-app-performance.monitor-application-instrumentation
+title: Exercise - Monitor an application with autoinstrumentation
+metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
+  title: Exercise - Monitor an application with autoinstrumentation
+  description: "Exercise - Monitor an application with autoinstrumentation"
+  ms.date: 06/30/2025
+  author: wwlpublish
+  ms.author: jeffko
+  ms.topic: unit
+  ms.custom:
+  - N/A
+durationInMinutes: 20
+content: |
+  [!include[](includes/6a-monitor-application-instrumentation.md)]
diff --git a/learn-pr/azure/monitor-app-performance/7-knowledge-check.yml b/learn-pr/azure/monitor-app-performance/7-knowledge-check.yml
@@ -1,39 +1,40 @@
-### YamlMime:ModuleUnit
-uid: learn.wwl.monitor-app-performance.knowledge-check
-title: Module assessment
-metadata:
-  title: Module assessment
-  description: "Knowledge check"
-  ms.date: 07/18/2024
-  author: wwlpublish
-  ms.author: jeffko
-  ms.topic: unit
-  ms.custom:
-  - N/A
-  module_assessment: true
-durationInMinutes: 3
-quiz:
-  title: "Check your knowledge"
-  questions:
-  - content: "Which of the following availability tests is recommended for authentication tests?"
-    choices:
-    - content: "URL ping"
-      isCorrect: false
-      explanation: "Incorrect. The URL ping test is used to test endpoint availability."
-    - content: "Standard"
-      isCorrect: false
-      explanation: "Incorrect. This single request test is similar to the URL ping test, but it includes additional information."
-    - content: "Custom TrackAvailability"
-      isCorrect: true
-      explanation: "Correct. Custom TrackAvailability test is the long term supported solution for multi request or authentication test scenarios."
-  - content: "Which of the following metric collection types provides near real-time querying and alerting on dimensions of metrics, and more responsive dashboards?"
-    choices:
-    - content: "Log-based"
-      isCorrect: false
-      explanation: "Incorrect. Log-based metrics are aggregated at query time and require more processing to produce results."
-    - content: "Pre-aggregated"
-      isCorrect: true
-      explanation: "Correct. Pre-aggregated metrics are stored as a time series and only with key dimensions, which enable near real-time alerting on dimensions of metrics, more responsive dashboards."
-    - content: "Azure Service Bus"
-      isCorrect: false
-      explanation: "Incorrect. Azure Service Bus is message queueing service."
+### YamlMime:ModuleUnit
+uid: learn.wwl.monitor-app-performance.knowledge-check
+title: Module assessment
+metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
+  title: Module assessment
+  description: "Knowledge check"
+  ms.date: 06/30/2025
+  author: wwlpublish
+  ms.author: jeffko
+  ms.topic: unit
+  ms.custom:
+  - N/A
+durationInMinutes: 3
+quiz:
+  title: "Check your knowledge"
+  questions:
+  - content: "Which of the following availability tests is recommended for authentication tests?"
+    choices:
+    - content: "URL ping"
+      isCorrect: false
+      explanation: "Incorrect. The URL ping test is used to test endpoint availability."
+    - content: "Standard"
+      isCorrect: false
+      explanation: "Incorrect. This single request test is similar to the URL ping test, but it includes additional information."
+    - content: "Custom TrackAvailability"
+      isCorrect: true
+      explanation: "Correct. Custom TrackAvailability test is the long term supported solution for multi request or authentication test scenarios."
+  - content: "Which of the following metric collection types provides near real-time querying and alerting on dimensions of metrics, and more responsive dashboards?"
+    choices:
+    - content: "Log-based"
+      isCorrect: false
+      explanation: "Incorrect. Log-based metrics are aggregated at query time and require more processing to produce results."
+    - content: "Preaggregated"
+      isCorrect: true
+      explanation: "Correct. Preaggregated metrics are stored as a time series and only with key dimensions, which enable near real-time alerting on dimensions of metrics, more responsive dashboards."
+    - content: "Azure Service Bus"
+      isCorrect: false
+      explanation: "Incorrect. Azure Service Bus is message queueing service."
diff --git a/learn-pr/azure/monitor-app-performance/8-summary.yml b/learn-pr/azure/monitor-app-performance/8-summary.yml
@@ -1,15 +1,17 @@
-### YamlMime:ModuleUnit
-uid: learn.wwl.monitor-app-performance.summary
-title: Summary
-metadata:
-  title: Summary
-  description: "Summary"
-  ms.date: 07/18/2024
-  author: wwlpublish
-  ms.author: jeffko
-  ms.topic: unit
-  ms.custom:
-  - N/A
-durationInMinutes: 3
-content: |
-  [!include[](includes/8-summary.md)]
+### YamlMime:ModuleUnit
+uid: learn.wwl.monitor-app-performance.summary
+title: Summary
+metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
+  title: Summary
+  description: "Summary"
+  ms.date: 06/30/2025
+  author: wwlpublish
+  ms.author: jeffko
+  ms.topic: unit
+  ms.custom:
+  - N/A
+durationInMinutes: 3
+content: |
+  [!include[](includes/8-summary.md)]
diff --git a/learn-pr/azure/monitor-app-performance/includes/1-introduction.md b/learn-pr/azure/monitor-app-performance/includes/1-introduction.md
@@ -5,3 +5,4 @@ After completing this module, you'll be able to:
 * Describe how Application Insights works and how it collects events and metrics.
 * Instrument an app for monitoring, and perform availability tests.
 * Use Application Map to help you monitor performance and troubleshoot issues.
+
diff --git a/learn-pr/azure/monitor-app-performance/includes/2-application-insights-overview.md b/learn-pr/azure/monitor-app-performance/includes/2-application-insights-overview.md
@@ -46,4 +46,4 @@ There are several ways to get started monitoring and analyzing app performance:
 * **At development time:** add Application Insights to your code. Allows you to customize telemetry collection and send more telemetry.
 * **Instrument your web pages** for page view, AJAX, and other client-side telemetry.
 * **Analyze mobile app usage** by integrating with Visual Studio App Center.
-* **Availability tests** - ping your website regularly from our servers.
+* **Availability tests** - ping your website regularly from our servers.
diff --git a/learn-pr/azure/monitor-app-performance/includes/3-logs-based-metrics.md b/learn-pr/azure/monitor-app-performance/includes/3-logs-based-metrics.md
@@ -15,13 +15,14 @@ At the same time, collecting a complete set of events may be impractical (or eve
 
 ## Preaggregated metrics
 
-The preaggregated metrics aren't stored as individual events with lots of properties. Instead, they're stored as preaggregated time series, and only with key dimensions. This makes the new metrics superior at query time: retrieving data happens faster and requires less compute power. This enables new scenarios such as near real-time alerting on dimensions of metrics, more responsive dashboards, and more.
+The preaggregated metrics aren't stored as individual events with lots of properties. Instead, they're stored as preaggregated time series, and only with key dimensions. This feature makes the new metrics superior at query time: retrieving data happens faster and requires less compute power. It also enables new scenarios such as near real-time alerting on dimensions of metrics, more responsive dashboards, and more.
 
 > [!IMPORTANT]
-> Both, log-based and pre-aggregated metrics coexist in Application Insights. To differentiate the two, in the Application Insights UX the pre-aggregated metrics are now called "Standard metrics (preview)", while the traditional metrics from the events were renamed to "Log-based metrics".
+> Both, log-based and pre-aggregated metrics coexist in Application Insights. To differentiate the two, in the Application Insights UX the pre-aggregated metrics are now called *Standard metrics (preview)*, while the traditional metrics from the events were renamed to *Log-based metrics*.
 
 The newer SDKs ([Application Insights 2.7](https://www.nuget.org/packages/Microsoft.ApplicationInsights/2.7.2) SDK or later for .NET) preaggregate metrics during collection. This applies to  [standard metrics sent by default](/azure/azure-monitor/essentials/metrics-supported#microsoftinsightscomponents) so the accuracy isn't affected by sampling or filtering. It also applies to custom metrics sent using [GetMetric](/azure/azure-monitor/app/api-custom-events-metrics#getmetric) resulting in less data ingestion and lower cost.
 
 For the SDKs that don't implement preaggregation the Application Insights backend still populates the new metrics by aggregating the events received by the Application Insights event collection endpoint. While you don't benefit from the reduced volume of data transmitted over the wire, you can still use the preaggregated metrics and experience better performance and support of the near real-time dimensional alerting with SDKs that don't preaggregate metrics during collection.
 
 It's worth mentioning that the collection endpoint preaggregates events before ingestion sampling, which means that [ingestion sampling](/azure/azure-monitor/app/sampling) will never impact the accuracy of preaggregated metrics, regardless of the SDK version you use with your application.
+
diff --git a/learn-pr/azure/monitor-app-performance/includes/4-app-instrumentation.md b/learn-pr/azure/monitor-app-performance/includes/4-app-instrumentation.md
@@ -5,7 +5,7 @@ At a basic level, "instrumenting" is simply enabling an application to capture t
 
 **Autoinstrumentation** enables telemetry collection through configuration without touching the application's code. Although it's more convenient, it tends to be less configurable. It's also not available in all languages. See [Autoinstrumentation supported environments and languages](/azure/azure-monitor/app/codeless-overview). When autoinstrumentation is available, it's the easiest way to enable Azure Monitor Application Insights.
 
-**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:
+**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 aren't captured by default with autoinstrumentation. There are two options for manual instrumentation:
 
 *   [Application Insights SDKs](/azure/azure-monitor/app/asp-net-core)
 *   [Azure Monitor OpenTelemetry Distros](/azure/azure-monitor/app/opentelemetry-enable).
@@ -39,3 +39,4 @@ Some legacy terms in Application Insights are confusing because of the industry
 | Operation ID | Trace ID |
 | ID or Operation Parent ID | Span ID |
 
+
diff --git a/learn-pr/azure/monitor-app-performance/includes/5-availability-tests.md b/learn-pr/azure/monitor-app-performance/includes/5-availability-tests.md
@@ -12,3 +12,4 @@ You can create up to 100 availability tests per Application Insights resource, a
 
 > [!IMPORTANT]
 > **URL ping tests:** On September 30, 2026, URL ping tests in Application Insights will be retired. Existing URL ping tests will be removed from your resources. Review the [pricing](https://azure.microsoft.com/pricing/details/monitor) for standard tests and [transition](https://aka.ms/availabilitytestmigration) to using them before September 30, 2026 to ensure you can continue to run single-step availability tests in your Application Insights resources.
+
diff --git a/learn-pr/azure/monitor-app-performance/includes/6-application-map.md b/learn-pr/azure/monitor-app-performance/includes/6-application-map.md
diff --git a/learn-pr/azure/monitor-app-performance/includes/6a-monitor-application-instrumentation.md b/learn-pr/azure/monitor-app-performance/includes/6a-monitor-application-instrumentation.md
diff --git a/learn-pr/azure/monitor-app-performance/includes/8-summary.md b/learn-pr/azure/monitor-app-performance/includes/8-summary.md
diff --git a/learn-pr/azure/monitor-app-performance/index.yml b/learn-pr/azure/monitor-app-performance/index.yml
diff --git a/learn-pr/azure/monitor-app-performance/media/launch-exercise.png b/learn-pr/azure/monitor-app-performance/media/launch-exercise.png
