Skip to content

Commit 405bb1e

Browse files
committed
Adding tutorial to enable AI for ASP.NET Core
1 parent 165c30b commit 405bb1e

File tree

2 files changed

+10
-8
lines changed

2 files changed

+10
-8
lines changed

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

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
2-
title: Enable Azure Application Insights for ASP.NET Core applications | Microsoft Docs
3-
description: Tutorial to monitor ASP.NET Core web applications for availability, performance, and usage.
2+
title: Application Insights SDK for ASP.NET Core applications | Microsoft Docs
3+
description: Application Insights SDK tutorial to monitor ASP.NET Core web applications for availability, performance, and usage.
44
ms.topic: conceptual
55
ms.devlang: csharp
66
ms.custom: devx-track-csharp
7-
ms.date: 08/03/2022
7+
ms.date: 08/22/2022
88
ms.reviewer: casocha
99
---
1010

@@ -151,7 +151,7 @@ The Application Insights for ASP.NET Core web applications NuGet package encapsu
151151
![A code window displays with the preceding code snippet highlighted.](./media/tutorial-asp-net-core/enable-server-side-telemetry.png "Enable server-side telemetry")
152152

153153
> [!TIP]
154-
> Learn more about [configuration options in ASP.NET Core](/aspnet/core/fundamentals/configuration/?view=aspnetcore-6.0).
154+
> Learn more about [configuration options in ASP.NET Core](/aspnet/core/fundamentals/configuration).
155155

156156
## Enable client-side telemetry for web applications
157157

@@ -183,7 +183,7 @@ The preceding steps are enough to help you start collecting server-side telemetr
183183
```
184184

185185
> [!NOTE]
186-
> JavaScript injection provides a default configuration experience. If you require [configuration](./javascript.md#configuration) beyond setting the connection string, you are required to remove auto-injection as described above and manually add the [JavaScript SDK](./javascript.md#adding-the-javascript-sdk).
186+
> JavaScript injection provides a default configuration experience. If you require [configuration](./javascript.md#configuration) beyond setting the connection string, you are required to remove auto-injection as described above and manually add the [JavaScript SDK](./javascript.md#add-the-javascript-sdk).
187187

188188
## Enable monitoring of database queries
189189

@@ -337,15 +337,15 @@ public class ValuesController : ControllerBase
337337
}
338338
```
339339

340-
For more information, see [Logging in ASP.NET Core](/aspnet/core/fundamentals/logging/?view=aspnetcore-6.0).
340+
For more information, see [Logging in ASP.NET Core](/aspnet/core/fundamentals/logging).
341341

342342
## View logs in Application Insights
343343

344344
The ValuesController above is deployed with the sample application and is located in the **Controllers** folder of the project.
345345

346346
1. Using an internet browser, open the sample application. In the address bar, append `/api/Values` and press <kbd>Enter</kbd>.
347347

348-
![A browser window displays with /api/Values appended to the URL in the address bar.](media/asp-net-core/values-api-url.png "Values API URL")
348+
![A browser window displays with /api/Values appended to the URL in the address bar.](media/tutorial-asp-net-core/values-api-url.png "Values API URL")
349349

350350
2. Wait a few moments, then return to the **Application Insights** resource in the [Azure Portal](https://portal.azure.com).
351351

@@ -369,7 +369,7 @@ The ValuesController above is deployed with the sample application and is locate
369369
370370
## Control the level of logs sent to Application Insights
371371
372-
`ILogger` implementations have a built-in mechanism to apply [log filtering](/dotnet/core/extensions/logging#how-filtering-rules-are-applied). This filtering lets you control the logs that are sent to each registered provider, including the Application Insights provider. You can use the filtering either in configuration (using an *appsettings.json* file) or in code. For more information about log levels and guidance on appropriate use, see the [Log Level](/aspnet/core/fundamentals/logging/?view=aspnetcore-6.0#log-level) documentation.
372+
`ILogger` implementations have a built-in mechanism to apply [log filtering](/dotnet/core/extensions/logging#how-filtering-rules-are-applied). This filtering lets you control the logs that are sent to each registered provider, including the Application Insights provider. You can use the filtering either in configuration (using an *appsettings.json* file) or in code. For more information about log levels and guidance on appropriate use, see the [Log Level](/aspnet/core/fundamentals/logging#log-level) documentation.
373373
374374
The following examples show how to apply filter rules to the `ApplicationInsightsLoggerProvider` to control the level of logs sent to Application Insights.
375375

articles/azure-monitor/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -35,6 +35,8 @@ items:
3535
href: vm/tutorial-monitor-vm-guest.md
3636
- name: Application Insights
3737
items:
38+
- name: Application Insights SDK for ASP.NET Core applications
39+
href: app/tutorial-asp-net-core.md
3840
- name: Find application run-time exceptions
3941
href: app/tutorial-runtime-exceptions.md
4042
- name: Find application performance issues

0 commit comments

Comments
 (0)