Merge pull request #234843 from AaronMaxwell/aaronmax-asp-net-trace-logs-search-fix

https://github.com/MicrosoftDocs/azure-docs/issues/108234

Author: prmerger-automator[bot]

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

@@ -4,14 +4,13 @@ description: Search logs generated by Trace, NLog, or Log4Net.
 ms.topic: conceptual
 ms.devlang: csharp
 ms.custom: devx-track-csharp
-ms.date: 03/22/2023
+ms.date: 04/18/2023
 ms.reviewer: casocha
 ---
 
-
 # Explore .NET/.NET Core and Python trace logs in Application Insights
 
-Send diagnostic tracing logs for your ASP.NET/ASP.NET Core application from ILogger, NLog, log4Net, or System.Diagnostics.Trace to [Azure Application Insights][start]. For Python applications, send diagnostic tracing logs by using AzureLogHandler in OpenCensus Python for Azure Monitor. You can then explore and search for them. Those logs are merged with the other log files from your application. You can use them to identify traces that are associated with each user request and correlate them with other events and exception reports.
+Send diagnostic tracing logs for your ASP.NET/ASP.NET Core application from ILogger, NLog, log4Net, or System.Diagnostics.Trace to Azure Application Insights. For Python applications, send diagnostic tracing logs by using AzureLogHandler in OpenCensus Python for Azure Monitor. You can then explore and search for them. Those logs are merged with the other log files from your application. You can use them to identify traces that are associated with each user request and correlate them with other events and exception reports.
 
 > [!NOTE]
 > 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 calling [**Application Insights TrackTrace()**](./api-custom-events-metrics.md#tracktrace) directly.
@@ -38,7 +37,7 @@ Install your chosen logging framework in your project, which should result in an
 
 ## Configure Application Insights to collect logs
 
-[Add Application Insights to your project](./asp-net.md) if you haven't done that yet. You'll see an option to include the log collector.
+[Add Application Insights to your project](./asp-net.md) if you haven't done that yet and there is an option to include the log collector.
 
 Or right-click your project in Solution Explorer to **Configure Application Insights**. Select the **Configure trace collection** option.
 
@@ -167,7 +166,7 @@ You can also add a severity level to your message. And, like other telemetry, yo
                               new Dictionary<string, string> { { "database", "db.ID" } });
   ```
 
-Now you can easily filter out in [Search][diagnostic] all the messages of a particular severity level that relate to a particular database.
+Now you can easily filter out in **Transaction Search** all the messages of a particular severity level that relate to a particular database.
 
 ## AzureLogHandler for OpenCensus Python
 
@@ -191,7 +190,7 @@ logger.warning('Hello, World!')
 
 Run your app in debug mode or deploy it live.
 
-In your app's overview pane in the [Application Insights portal][portal], select [Search][diagnostic].
+In your app's overview pane in the Application Insights portal, select **Transaction Search**.
 
 You can, for example:
 
@@ -231,7 +230,7 @@ The Application Insights Java agent collects logs from Log4j, Logback, and java.
 
 ### <a name="emptykey"></a>Why do I get the "Instrumentation key cannot be empty" error message?
 
-You probably installed the logging adapter NuGet package without installing Application Insights. In Solution Explorer, right-click *ApplicationInsights.config*, and select **Update Application Insights**. You'll be prompted to sign in to Azure and create an Application Insights resource or reuse an existing one. That should fix the problem.
+You probably installed the logging adapter NuGet package without installing Application Insights. In Solution Explorer, right-click *ApplicationInsights.config*, and select **Update Application Insights**. You are prompted to sign in to Azure and create an Application Insights resource or reuse an existing one. It should fix the problem.
 
 ### Why can I see traces but not other events in diagnostic search?
 
@@ -247,10 +246,9 @@ Perhaps your application sends voluminous amounts of data and you're using the A
 
 ## <a name="add"></a>Next steps
 
-* [Diagnose failures and exceptions in ASP.NET][exceptions]
-* [Learn more about Search][diagnostic]
-* [Set up availability and responsiveness tests][availability]
-* [Troubleshooting][qna]
+* [Diagnose failures and exceptions in ASP.NET](asp-net-exceptions.md)
+* [Learn more about Transaction Search](diagnostic-search.md)
+* [Set up availability and responsiveness tests](availability-overview.md)
 
 <!--Link references-->