few more

Author: cijothomas

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

@@ -28,6 +28,7 @@ The [Application Insights SDK for ASP.NET Core](https://nuget.org/packages/Micro
 * **Deployment method**: Framework dependent or self-contained.
 * **Web server**: IIS (Internet Information Server) or Kestrel.
 * **Hosting platform**: The Web Apps feature of Azure App Service, Azure VM, Docker, Azure Kubernetes Service (AKS), and so on.
+* **.NET Core Runtime version**: 1.XX, 2.XX or 3.XX
 * **IDE**: Visual Studio, VS Code, or command line.
 
 > [!NOTE]
@@ -356,9 +357,14 @@ Note that the above does not prevent any auto collection modules from collecting
 
 ## Frequently asked questions
 
+### Does Application Insights support ASP.NET Core 3.0?
+
+Yes. Update to [Application Insights SDK for ASP.NET Core](https://nuget.org/packages/Microsoft.ApplicationInsights.AspNetCore) version 2.8.0 or higher. Older versions of the SDK do not support ASP.NET Core 3.0.
+Also, if you are using Visual Studio based instructions from [here](#enable-application-insights-server-side-telemetry-visual-studio), please update to the latest version of Visual Studio 2019 (16.3.0) to onboard. Previous versions of Visual Studio do not support automatic onboarding.
+
 ### How can I track telemetry that's not automatically collected?
 
-Get an instance of `TelemetryClient` by using constructor injection, and call the required `TrackXXX()` method on it. We don't recommend creating new `TelemetryClient` instances in an ASP.NET Core application. A singleton instance of `TelemetryClient` is already registered in the `DependencyInjection` container, which shares `TelemetryConfiguration` with rest of the telemetry. Creating a new `TelemetryClient` instance is recommended only if it needs a configuration that's separate from the rest of the telemetry. 
+Get an instance of `TelemetryClient` by using constructor injection, and call the required `TrackXXX()` method on it. We don't recommend creating new `TelemetryClient` instances in an ASP.NET Core application. A singleton instance of `TelemetryClient` is already registered in the `DependencyInjection` container, which shares `TelemetryConfiguration` with rest of the telemetry. Creating a new `TelemetryClient` instance is recommended only if it needs a configuration that's separate from the rest of the telemetry.
 
 The following example shows how to track additional telemetry from a controller.
 
@@ -389,7 +395,7 @@ For more information about custom data reporting in Application Insights, see [A
 
 Yes, enabling Application Insights with this method is valid. This technique is used in Visual Studio onboarding and in the Web Apps extensions. However, we recommend using `services.AddApplicationInsightsTelemetry()` because it provides overloads to control some configuration. Both methods do the same thing internally, so if you don't need to apply custom configuration, you can call either method.
 
-`IWebHostBuilder` is replaced with `IHostBuilder` in ASP.NET Core 3.0, and to avoid confusion, Application Insights version 2.8.0-beta3 onwards is marking the UseApplicationInsights() method as obsolete, and will be removed in the next major version.
+`IWebHostBuilder` is replaced with `IHostBuilder` in ASP.NET Core 3.0, and to avoid confusion, Application Insights version 2.8.0 onwards is marking the UseApplicationInsights() method as obsolete, and will be removed in the next major version.
 
 ### I'm deploying my ASP.NET Core application to Web Apps. Should I still enable the Application Insights extension from Web Apps?
 

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

@@ -321,6 +321,9 @@ Below is our step-by-step troubleshooting guide for extension/agent based monito
 > [!NOTE]
 > Java and Node.js applications are only supported on Azure App Services via manual SDK based instrumentation and therefore the steps below do not apply to these scenarios.
 
+> [!NOTE]
+> ASP.NET Core 3.0 applications are not supported. Please follow [Manual instrumentation](https://docs.microsoft.com/azure/azure-monitor/app/asp-net-core) via code for ASP.NET Core 3.0 apps.
+
 1. Check that the application is monitored via `ApplicationInsightsAgent`.
     * Check that `ApplicationInsightsAgent_EXTENSION_VERSION` app setting is set to a value of "~2".
 2. Ensure that the application meets the requirements to be monitored.

articles/azure-monitor/app/eventcounters.md

@@ -15,7 +15,7 @@ ms.author: cithomas
 ---
 # EventCounters introduction
 
-`EventCounter` is .NET/.NET Core mechanism to publish and consume counters or statistics. [This](https://github.com/dotnet/corefx/blob/master/src/System.Diagnostics.Tracing/documentation/EventCounterTutorial.md) document gives an overview of `EventCounters` and examples on how to publish and consume them. EventCounters are supported in all OS Platforms - Windows, Linux and MacOS. It can be thought of as a cross-platform equivalent for the [PerformanceCounters](https://docs.microsoft.com/dotnet/api/system.diagnostics.performancecounter) that is only supported in Windows systems.
+`EventCounter` is .NET/.NET Core mechanism to publish and consume counters or statistics. [This](https://github.com/dotnet/corefx/blob/master/src/System.Diagnostics.Tracing/documentation/EventCounterTutorial.md) document gives an overview of `EventCounters` and examples on how to publish and consume them. EventCounters are supported in all OS Platforms - Windows, Linux, and MacOS. It can be thought of as a cross-platform equivalent for the [PerformanceCounters](https://docs.microsoft.com/dotnet/api/system.diagnostics.performancecounter) that is only supported in Windows systems.
 
 While users can publish any custom `EventCounters` to meet their needs, the .NET Core 3.0 runtime publishes a set of these counters by default. The document will walk through the steps required to collect and view `EventCounters` (system defined or user defined) in Azure Application Insights.
 
@@ -25,7 +25,7 @@ Application Insights supports collecting `EventCounters` with its `EventCounterC
 
 ## Default counters collected
 
-For apps running in .NET Core 3.0, the following set of counters are collected automatically by the SDK. The name of the counters will be of the form "Category|Counter".
+For apps running in .NET Core 3.0, the following counters are collected automatically by the SDK. The name of the counters will be of the form "Category|Counter".
 
 |Category | Counter|
 |---------------|-------|
@@ -129,10 +129,23 @@ Like other metrics, you can [set an alert](../../azure-monitor/app/alerts.md) to
 
 ## Frequently asked questions
 
-### Can I see EventCounters in Live Metrics ?
+### Can I see EventCounters in Live Metrics?
 
 No. Live Metrics do not show EventCounters as of today. Use Metric Explorer or Analytics to see the telemetry.
 
+### Which platforms can I see the default list of .NET Core 3.0 counters?
+
+EventCounter do not require any special permissions, and is supported in all platforms .NET Core 3.0 is supported. This includes:
+* **Operating system**: Windows, Linux, or Mac.
+* **Hosting method**: In process or out of process.
+* **Deployment method**: Framework dependent or self-contained.
+* **Web server**: IIS (Internet Information Server) or Kestrel.
+* **Hosting platform**: The Web Apps feature of Azure App Service, Azure VM, Docker, Azure Kubernetes Service (AKS), and so on.
+
+### I have enabled Application Insights from Azure Web App Portal. But I cannot see EventCounters.?
+
+ [Application Insights extension](https://docs.microsoft.com/azure/azure-monitor/app/azure-web-apps) for Asp.Net Core does not yet support this feature. This documetn will be updated when this feature is supported.
+
 ## <a name="next"></a>Next steps
 
 * [Dependency tracking](../../azure-monitor/app/asp-net-dependencies.md)