Skip to content

Commit 20cd11f

Browse files
newincludes
1 parent 850dfc2 commit 20cd11f

9 files changed

+24
-0
lines changed

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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,9 @@ ms.custom: mvc
1010
# What is Application Insights?
1111
Application Insights, a feature of [Azure Monitor](../overview.md), is an extensible Application Performance Management (APM) service for developers and DevOps professionals. Use it to monitor your live applications. It will automatically detect performance anomalies, and includes powerful analytics tools to help you diagnose issues and to understand what users actually do with your app. It's designed to help you continuously improve performance and usability. It works for apps on a wide variety of platforms including .NET, Node.js, Java, and Python hosted on-premises, hybrid, or any public cloud. It integrates with your DevOps process, and has connection points to a variety of development tools. It can monitor and analyze telemetry from mobile apps by integrating with Visual Studio App Center.
1212

13+
[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
14+
15+
1316
## How does Application Insights work?
1417
You install a small instrumentation package (SDK) in your application or enable Application Insights using the Application Insights Agent when [supported](./platforms.md). The instrumentation monitors your app and directs the telemetry data to an Azure Application Insights Resource using a unique GUID that we refer to as an Instrumentation Key.
1518

articles/azure-monitor/app/app-map.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,9 @@ ms.reviewer: sdash
1313

1414
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.
1515

16+
[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
17+
18+
1619
## What is a Component?
1720

1821
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.

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

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,8 @@ The example we'll use here is an [MVC application](/aspnet/core/tutorials/first-
1717
> [!NOTE]
1818
> A preview [OpenTelemetry-based .NET offering](opentelemetry-enable.md?tabs=net) is available. [Learn more](opentelemetry-overview.md).
1919
20+
[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
21+
2022
## Supported scenarios
2123

2224
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:

articles/azure-monitor/app/asp-net-trace-logs.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,9 @@ Send diagnostic tracing logs for your ASP.NET/ASP.NET Core application from ILog
1616
> 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.
1717
>
1818
>
19+
20+
[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
21+
1922
## Install logging on your app
2023
Install your chosen logging framework in your project, which should result in an entry in app.config or web.config.
2124

articles/azure-monitor/app/asp-net-troubleshoot-no-data.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,9 @@ ms.date: 05/21/2020
1010

1111
# Troubleshooting no data - Application Insights for .NET/.NET Core
1212

13+
[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
14+
15+
1316
## Some of my telemetry is missing
1417
*In Application Insights, I only see a fraction of the events that are being generated by my app.*
1518

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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,9 @@ This procedure configures your ASP.NET web app to send telemetry to the [Applica
1515
> [!NOTE]
1616
> A preview [OpenTelemetry-based .NET offering](opentelemetry-enable.md?tabs=net) is available. [Learn more](opentelemetry-overview.md).
1717
18+
[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
19+
20+
1821
## Prerequisites
1922
To add Application Insights to your ASP.NET website, you need to:
2023

articles/azure-monitor/app/azure-ad-authentication.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,8 @@ Below are SDKs/scenarios not supported in the Public Preview:
2525
- [Availability tests](availability-overview.md).
2626
- [Profiler](profiler-overview.md).
2727

28+
[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
29+
2830
## Prerequisites to enable Azure AD authentication ingestion
2931

3032
- Familiarity with:

articles/azure-monitor/app/azure-web-apps-net-core.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,9 @@ ms.custom: devx-track-dotnet
1111

1212
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.
1313

14+
[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
15+
16+
1417
## Enable agent-based monitoring
1518

1619
# [Windows](#tab/Windows)

articles/azure-monitor/app/azure-web-apps-net.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,8 @@ Enabling monitoring on your ASP.NET based web applications running on [Azure App
1717
> [!NOTE]
1818
> 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.
1919
20+
[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
21+
2022
## Enable agent-based monitoring
2123

2224
> [!NOTE]

0 commit comments

Comments
 (0)