Merge pull request #191287 from JasonAndrewWriter/1st25insightinclues

denrea · web-flow · commit 462a3f7e4c9c · 2022-03-14T14:49:59.000-07:00
1st20insightincluesfordepreication
diff --git a/articles/azure-monitor/app/app-map.md b/articles/azure-monitor/app/app-map.md
@@ -12,6 +12,9 @@ ms.reviewer: sdash
 
 Application Map helps you spot performance bottlenecks or failure hotspots across all components of your distributed application. Each node on the map represents an application component or its dependencies; and has health KPI and alerts status. You can click through from any component to more detailed diagnostics, such as Application Insights events. If your app uses Azure services, you can also click through to Azure diagnostics, such as SQL Database Advisor recommendations.
 
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
+
 ## What is a Component?
 
 Components are independently deployable parts of your distributed/microservices application. Developers and operations teams have code-level visibility or access to telemetry generated by these application components.
diff --git a/articles/azure-monitor/app/asp-net-core.md b/articles/azure-monitor/app/asp-net-core.md
@@ -16,6 +16,8 @@ The example we'll use here is an [MVC application](/aspnet/core/tutorials/first-
 > [!NOTE]
 > A preview [OpenTelemetry-based .NET offering](opentelemetry-enable.md?tabs=net) is available. [Learn more](opentelemetry-overview.md).
 
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
 ## Supported scenarios
 
 The [Application Insights SDK for ASP.NET Core](https://nuget.org/packages/Microsoft.ApplicationInsights.AspNetCore) can monitor your applications no matter where or how they run. If your application is running and has network connectivity to Azure, telemetry can be collected. Application Insights monitoring is supported everywhere .NET Core is supported. Support covers the following:
diff --git a/articles/azure-monitor/app/asp-net-trace-logs.md b/articles/azure-monitor/app/asp-net-trace-logs.md
@@ -15,6 +15,9 @@ Send diagnostic tracing logs for your ASP.NET/ASP.NET Core application from ILog
 > Do you need the log-capture module? It's a useful adapter for third-party loggers. But if you aren't already using NLog, log4Net, or System.Diagnostics.Trace, consider just calling [**Application Insights TrackTrace()**](./api-custom-events-metrics.md#tracktrace) directly.
 >
 >
+
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
 ## Install logging on your app
 Install your chosen logging framework in your project, which should result in an entry in app.config or web.config.
 
diff --git a/articles/azure-monitor/app/asp-net-troubleshoot-no-data.md b/articles/azure-monitor/app/asp-net-troubleshoot-no-data.md
@@ -9,6 +9,9 @@ ms.date: 05/21/2020
 
 # Troubleshooting no data - Application Insights for .NET/.NET Core
 
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
+
 ## Some of my telemetry is missing
 *In Application Insights, I only see a fraction of the events that are being generated by my app.*
 
diff --git a/articles/azure-monitor/app/asp-net.md b/articles/azure-monitor/app/asp-net.md
@@ -14,6 +14,8 @@ This procedure configures your ASP.NET web app to send telemetry to the [Applica
 > [!NOTE]
 > A preview [OpenTelemetry-based .NET offering](opentelemetry-enable.md?tabs=net) is available. [Learn more](opentelemetry-overview.md).
 
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
 ## Prerequisites
 To add Application Insights to your ASP.NET website, you need to:
 
diff --git a/articles/azure-monitor/app/azure-ad-authentication.md b/articles/azure-monitor/app/azure-ad-authentication.md
@@ -25,6 +25,8 @@ Below are SDKs/scenarios not supported in the Public Preview:
 - [Availability tests](availability-overview.md).
 - [Profiler](profiler-overview.md).
 
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
 ## Prerequisites to enable Azure AD authentication ingestion
 
 - Familiarity with:
diff --git a/articles/azure-monitor/app/azure-web-apps-net-core.md b/articles/azure-monitor/app/azure-web-apps-net-core.md
@@ -11,6 +11,9 @@ ms.custom: devx-track-dotnet
 
 Enabling monitoring on your ASP.NET Core based web applications running on [Azure App Services](../../app-service/index.yml) is now easier than ever. Whereas previously you needed to manually instrument your app, the latest extension/agent is now built into the App Service image by default. This article will walk you through enabling Azure Monitor application Insights monitoring as well as provide preliminary guidance for automating the process for large-scale deployments.
 
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
+
 ## Enable agent-based monitoring
 
 # [Windows](#tab/Windows)
diff --git a/articles/azure-monitor/app/azure-web-apps-net.md b/articles/azure-monitor/app/azure-web-apps-net.md
@@ -17,6 +17,8 @@ Enabling monitoring on your ASP.NET based web applications running on [Azure App
 > [!NOTE]
 > If both agent-based monitoring and manual SDK-based instrumentation is detected, only the manual instrumentation settings will be honored. This is to prevent duplicate data from being sent. To learn more about this, check out the [troubleshooting section](#troubleshooting) below.
 
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
 ## Enable agent-based monitoring
 
 > [!NOTE]
diff --git a/articles/azure-monitor/app/cloudservices.md b/articles/azure-monitor/app/cloudservices.md
@@ -12,6 +12,8 @@ ms.date: 09/05/2018
 
 ![Overview dashboard](./media/cloudservices/overview-graphs.png)
 
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
 ## Prerequisites
 Before you begin, you need:
 
diff --git a/articles/azure-monitor/app/configuration-with-applicationinsights-config.md b/articles/azure-monitor/app/configuration-with-applicationinsights-config.md
@@ -25,6 +25,9 @@ This document describes the sections you see in the configuration file, how they
 > [!NOTE]
 > ApplicationInsights.config and .xml instructions do not apply to the .NET Core SDK. For configuring .NET Core applications, follow [this](./asp-net-core.md) guide.
 
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
+
 ## Telemetry Modules (ASP.NET)
 Each Telemetry Module collects a specific type of data and uses the core API to send the data. The modules are installed by different NuGet packages, which also add the required lines to the .config file.
 
diff --git a/articles/azure-monitor/app/console.md b/articles/azure-monitor/app/console.md
@@ -17,6 +17,9 @@ You need a subscription with [Microsoft Azure](https://azure.com). Sign in with
 > [!NOTE]
 > It is *highly recommended* to use the [Microsoft.ApplicationInsights.WorkerService](https://www.nuget.org/packages/Microsoft.ApplicationInsights.WorkerService) package and associated instructions from [here](./worker-service.md) for any Console Applications. This package targets [`NetStandard2.0`](/dotnet/standard/net-standard), and hence can be used in .NET Core 2.1 or higher, and .NET Framework 4.7.2 or higher.
 
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
+
 ## Getting started
 
 > [!IMPORTANT]
diff --git a/articles/azure-monitor/app/correlation.md b/articles/azure-monitor/app/correlation.md
@@ -14,6 +14,9 @@ In the world of microservices, every logical operation requires work to be done
 
 This article explains the data model used by Application Insights to correlate telemetry sent by multiple components. It covers context-propagation techniques and protocols. It also covers the implementation of correlation tactics on different languages and platforms.
 
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
+
 ## Data model for telemetry correlation
 
 Application Insights defines a [data model](../../azure-monitor/app/data-model.md) for distributed telemetry correlation. To associate telemetry with a logical operation, every telemetry item has a context field called `operation_Id`. This identifier is shared by every telemetry item in the distributed trace. So even if you lose telemetry from a single layer, you can still associate telemetry reported by other components.
diff --git a/articles/azure-monitor/app/create-new-resource.md b/articles/azure-monitor/app/create-new-resource.md
@@ -13,6 +13,8 @@ Azure Application Insights displays data about your application in a Microsoft A
 > [!IMPORTANT]
 > [Classic Application Insights has been deprecated](https://azure.microsoft.com/updates/we-re-retiring-classic-application-insights-on-29-february-2024/). Please follow these [instructions on how upgrade to workspace-based Application Insights](convert-classic-resource.md).
 
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
 ## Sign in to Microsoft Azure
 
 If you don't have an Azure subscription, create a [free](https://azure.microsoft.com/free/) account before you begin.
diff --git a/articles/azure-monitor/app/create-workspace-resource.md b/articles/azure-monitor/app/create-workspace-resource.md
@@ -15,6 +15,9 @@ This also allows for common Azure role-based access control (Azure RBAC) across
 > [!NOTE]
 > Data ingestion and retention for workspace-based Application Insights resources are billed through the Log Analytics workspace where the data is located. [Learn more]( ./pricing.md#workspace-based-application-insights) about billing for workspace-based Application Insights resources.
 
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
+
 ## New capabilities
 
 Workspace-based Application Insights allows you to take advantage of the latest capabilities of Azure Monitor and Log Analytics including:
diff --git a/articles/azure-monitor/app/custom-endpoints.md b/articles/azure-monitor/app/custom-endpoints.md
@@ -12,7 +12,10 @@ ms.custom: references_regions, devx-track-js
 To send data from Application Insights to certain regions, you'll need to override the default endpoint addresses. Each SDK requires slightly different modifications, all of which are described in this article. These changes require adjusting the sample code and replacing the placeholder values for `QuickPulse_Endpoint_Address`, `TelemetryChannel_Endpoint_Address`, and `Profile_Query_Endpoint_address` with the actual endpoint addresses for your specific region. The end of this article contains links to the endpoint addresses for regions where this configuration is required.
 
 > [!NOTE]
-> [Connection strings](./sdk-connection-string.md?tabs=net) are the new preferred method of setting custom endpoints within Application Insights.
+> [Connection strings](./sdk-connection-string.md?tabs=net) are the new preferred method of setting custom endpoints within Application Insights.   
+
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
 
 ---
 
diff --git a/includes/azure-monitor-instrumentation-key-deprecation.md b/includes/azure-monitor-instrumentation-key-deprecation.md
@@ -1,5 +1,5 @@
 ---
-title: "include file for instrumentation key depprecatiom" 
+title: "include file for instrumentation key depprecation" 
 description: "include file" 
 services: azure-monitor
 author: v-jandrew
@@ -10,5 +10,5 @@ ms.author: v-jandrew
 ms.custom: "include file"
 ---
 
->[!NOTE]
+>[!NOTE] 
 >On March 31st, 2025, support for instrumentation key ingestion will end. Instrumentation key ingestion will continue to work, but we’ll no longer provide updates or support for the feature. [Transition to connection strings](../articles/azure-monitor/app/migrate-from-instrumentation-keys-to-connection-strings.md) to remain supported. 

Original file line number	Diff line number	Diff line change
`@@ -15,6 +15,9 @@ Send diagnostic tracing logs for your ASP.NET/ASP.NET Core application from ILog`
`15`	`15`	`> Do you need the log-capture module? It's a useful adapter for third-party loggers. But if you aren't already using NLog, log4Net, or System.Diagnostics.Trace, consider just calling [Application Insights TrackTrace()](./api-custom-events-metrics.md#tracktrace) directly.`
`16`	`16`	`>`
`17`	`17`	`>`
	`18`	`+`
	`19`	`+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]`
	`20`	`+`
`18`	`21`	`## Install logging on your app`
`19`	`22`	`Install your chosen logging framework in your project, which should result in an entry in app.config or web.config.`
`20`	`23`