Tagging classic API docs and moving within TOC

Author: AarDavMax

articles/azure-monitor/app/asp-net-dependencies.md

@@ -10,10 +10,10 @@ ms.reviewer: mmcc
 
 # Dependency tracking in Application Insights
 
-A *dependency* is a component that's called by your application. It's typically a service called by using HTTP, a database, or a file system. [Application Insights](./app-insights-overview.md) measures the duration of dependency calls and whether it's failing or not, along with information like the name of the dependency. You can investigate specific dependency calls and correlate them to requests and exceptions.
-
 [!INCLUDE [azure-monitor-app-insights-otel-available-notification](../includes/azure-monitor-app-insights-otel-available-notification.md)]
 
+A *dependency* is a component that's called by your application. It's typically a service called by using HTTP, a database, or a file system. [Application Insights](./app-insights-overview.md) measures the duration of dependency calls and whether it's failing or not, along with information like the name of the dependency. You can investigate specific dependency calls and correlate them to requests and exceptions.
+
 ## Automatically tracked dependencies
 
 Application Insights SDKs for .NET and .NET Core ship with `DependencyTrackingTelemetryModule`, which is a telemetry module that automatically collects dependencies. This dependency collection is enabled automatically for [ASP.NET](./asp-net.md) and [ASP.NET Core](./asp-net-core.md) applications when it's configured according to the linked official docs. The module `DependencyTrackingTelemetryModule` is shipped as the [Microsoft.ApplicationInsights.DependencyCollector](https://www.nuget.org/packages/Microsoft.ApplicationInsights.DependencyCollector/) NuGet package. It's brought automatically when you use either the `Microsoft.ApplicationInsights.Web` NuGet package or the `Microsoft.ApplicationInsights.AspNetCore` NuGet package.

articles/azure-monitor/app/asp-net-exceptions.md

@@ -11,6 +11,8 @@ ms.reviewer: mmcc
 
 # Diagnose exceptions in web apps with Application Insights
 
+[!INCLUDE [azure-monitor-app-insights-otel-available-notification](../includes/azure-monitor-app-insights-otel-available-notification.md)]
+
 Exceptions in web applications can be reported with [Application Insights](./app-insights-overview.md). You can correlate failed requests with exceptions and other events on both the client and server so that you can quickly diagnose the causes. In this article, you'll learn how to set up exception reporting, report exceptions explicitly, diagnose failures, and more.
 
 ## Set up exception reporting

articles/azure-monitor/app/distributed-trace-data.md

@@ -11,6 +11,8 @@ ms.custom: devx-track-python, devx-track-csharp, devx-track-dotnet, devx-track-e
 
 # What is distributed tracing and telemetry correlation?
 
+[!INCLUDE [azure-monitor-app-insights-otel-available-notification](../includes/azure-monitor-app-insights-otel-available-notification.md)]
+
 Modern cloud and [microservices](https://azure.com/microservices) architectures have enabled simple, independently deployable services that reduce costs while increasing availability and throughput. However, it has made overall systems more difficult to reason about and debug. Distributed tracing solves this problem by providing a performance profiler that works like call stacks for cloud and microservices architectures.
 
 Azure Monitor provides two experiences for consuming distributed trace data: the [transaction diagnostics](./transaction-search-and-diagnostics.md?tabs=transaction-diagnostics) view for a single transaction/request and the [application map](./app-map.md) view to show how systems interact.

articles/azure-monitor/app/pre-aggregated-metrics-log-metrics.md

@@ -8,10 +8,10 @@ ms.reviewer: vitalyg
 
 # Log-based and pre-aggregated metrics in Application Insights
 
-This article explains the difference between "traditional" Application Insights metrics that are based on logs and pre-aggregated metrics. Both types of metrics are available to users of Application Insights. Each one brings a unique value in monitoring application health, diagnostics, and analytics. The developers who are instrumenting applications can decide which type of metric is best suited to a particular scenario. Decisions are based on the size of the application, expected volume of telemetry, and business requirements for metrics precision and alerting.
-
 [!INCLUDE [azure-monitor-app-insights-otel-available-notification](../includes/azure-monitor-app-insights-otel-available-notification.md)]
 
+This article explains the difference between "traditional" Application Insights metrics that are based on logs and pre-aggregated metrics. Both types of metrics are available to users of Application Insights. Each one brings a unique value in monitoring application health, diagnostics, and analytics. The developers who are instrumenting applications can decide which type of metric is best suited to a particular scenario. Decisions are based on the size of the application, expected volume of telemetry, and business requirements for metrics precision and alerting.
+
 ## Log-based metrics
 
 In the past, the application monitoring telemetry data model in Application Insights was solely based on a few predefined types of events, such as requests, exceptions, dependency calls, and page views. Developers can use the SDK to emit these events manually by writing code that explicitly invokes the SDK. Or they can rely on the automatic collection of events from autoinstrumentation. In either case, the Application Insights back end stores all collected events as logs. The Application Insights panes in the Azure portal act as an analytical and diagnostic tool for visualizing event-based data from logs.

articles/azure-monitor/app/sampling-classic-api.md

@@ -16,6 +16,8 @@ When metric counts are presented in the portal, they're renormalized to take int
 > [!NOTE]
 > - If you've adopted our OpenTelemetry Distro and are looking for configuration options, see [Enable Sampling](opentelemetry-configuration.md#enable-sampling).
 
+[!INCLUDE [azure-monitor-app-insights-otel-available-notification](../includes/azure-monitor-app-insights-otel-available-notification.md)]
+
 :::image type="content" source="./media/sampling/data-sampling.png" lightbox="./media/sampling/data-sampling.png" alt-text="A screenshot of sampling configuration options.":::
 
 ## Brief summary

articles/azure-monitor/app/sdk-connection-string.md

@@ -13,6 +13,8 @@ This article shows how to use connection strings.
 
 ## Overview
 
+[!INCLUDE [azure-monitor-app-insights-otel-available-notification](../includes/azure-monitor-app-insights-otel-available-notification.md)]
+
 Connection strings define where to send telemetry data.
 
 Key-value pairs provide an easy way for users to define a prefix suffix combination for each Application Insights service or product.

articles/azure-monitor/app/statsbeat.md

@@ -1,7 +1,7 @@
 ---
 title: Statsbeat in Application Insights | Microsoft Docs
 description: Statistics about Application Insights SDKs and AutoInstrumentation
-ms.topic: conceptual
+ms.topic: reference
 ms.date: 08/24/2022
 ms.custom: references_regions
 ms.reviwer: heya

articles/azure-monitor/toc.yml

@@ -160,12 +160,22 @@ items:
                 displayName: correlation, dependency, dependencies, track dependency, OWIN, queue, service bus, background tasks, long running background tasks, outgoing dependency tracking, parallel operations, System.Diagnostics.Activity, System.Diagnostics.DiagnosticSource, StartOperation, StopOperation
               - name: Performance counters
                 href: app/performance-counters.md
+              - name: Exceptions
+                href: app/asp-net-exceptions.md
+              - name: ASP.NET Dependencies
+                href: app/asp-net-dependencies.md
         - name: Node.js
           href: app/nodejs.md
         - name: Python OpenCensus (deprecated)
           href: /previous-versions/azure/azure-monitor/app/opencensus-python
         - name: Advanced SDK topics
           items:
+          - name: Connection strings
+            href: app/sdk-connection-string.md
+            displayName: connection string, instrumentation key
+          - name: Sampling
+            href: app/sampling-classic-api.md
+            displayName: adaptive sampling, fixed rate sample, fixed sampling, ingestion sampling
           - name: Application Insights API summary
             displayName: SDK, API, custom events, custom metrics, trackevent, trackmetric, getmetric, trackrequest, trackexception, tracktrace, trackdependency
             href: app/api-custom-events-metrics.md
@@ -174,6 +184,11 @@ items:
           - name: TelemetryProcessors
             displayName: processors, filtering, telemetry filtering, telemetry processor
             href: app/api-filtering-sampling.md
+          - name: Distributed tracing and telemetry correlation
+            href: app/distributed-trace-data.md
+            displayName: correlation headers, w3c, distributed tracing, tracing
+          - name: Log-based & pre-aggregated metrics
+            href: app/pre-aggregated-metrics-log-metrics.md
           - name: IP address collection
             href: app/ip-collection.md
             displayName: geolocation, IP collection, IP tracking, IP storage
@@ -1514,35 +1529,18 @@ items:
     href: agents/azure-monitor-agent-extension-versions.md
   - name: Application Insights
     items:
-    - name: Connection strings
-      href: app/sdk-connection-string.md
-      displayName: connection string, instrumentation key
     - name: Microsoft Entra authentication
       href: app/azure-ad-authentication.md
     - name: Application Insights data model
       href: app/data-model-complete.md
-    - name: Distributed tracing and telemetry correlation
-      href: app/distributed-trace-data.md
-      displayName: correlation headers, w3c, distributed tracing, tracing
-    - name: Sampling
-      href: app/sampling-classic-api.md
-      displayName: adaptive sampling, fixed rate sample, fixed sampling, ingestion sampling
     - name: Statsbeat
       href: app/statsbeat.md
-    - name: Log-based & pre-aggregated metrics
-      href: app/pre-aggregated-metrics-log-metrics.md
-    - name: Exceptions
-      href: app/asp-net-exceptions.md
-    - name: ASP.NET Dependencies
-      href: app/asp-net-dependencies.md
     - name: Metrics
       items:
       - name: Log-based metrics definitions
         href: essentials/app-insights-metrics.md
       - name: Standard metrics
         href: app/standard-metrics.md
-    - name: Azure Functions
-      href: ../azure-functions/functions-monitoring.md?toc=/azure/azure-monitor/toc.json
   - name: Azure PowerShell
     items:
     - name: Azure Monitor