Skip to content

Commit 35add7b

Browse files
authored
Merge pull request #97793 from mrbullwinkle/mrb_12_04_2019_app_service
article updates
2 parents 997e727 + a8e54bb commit 35add7b

File tree

1 file changed

+38
-6
lines changed

1 file changed

+38
-6
lines changed

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

Lines changed: 38 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.subservice: application-insights
66
ms.topic: conceptual
77
author: mrbullwinkle
88
ms.author: mbullwin
9-
ms.date: 10/04/2019
9+
ms.date: 12/19/2019
1010

1111
---
1212

@@ -33,7 +33,9 @@ There are two ways to enable application monitoring for Azure App Services hoste
3333
> [!NOTE]
3434
> 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](https://docs.microsoft.com/azure/azure-monitor/app/azure-web-apps#troubleshooting) below.
3535
36-
## Enable agent-based monitoring for .NET applications
36+
## Enable agent-based monitoring
37+
38+
# [.NET](#tab/net)
3739

3840
> [!NOTE]
3941
> The combination of APPINSIGHTS_JAVASCRIPT_ENABLED and urlCompression is not supported. For more info see the explanation in the [troubleshooting section](https://docs.microsoft.com/azure/azure-monitor/app/azure-web-apps#troubleshooting).
@@ -69,7 +71,7 @@ There are two ways to enable application monitoring for Azure App Services hoste
6971

7072
* For the list of supported adaptive sampling telemetry processor settings, you can consult the [code](https://github.com/Microsoft/ApplicationInsights-dotnet/blob/master/src/ServerTelemetryChannel/AdaptiveSamplingTelemetryProcessor.cs) and [associated documentation](https://docs.microsoft.com/azure/azure-monitor/app/sampling).
7173

72-
## Enable agent-based monitoring for .NET Core applications
74+
# [.NET Core](#tab/netcore)
7375

7476
The following versions of .NET Core are supported: ASP.NET Core 2.0, ASP.NET Core 2.1, ASP.NET Core 2.2
7577

@@ -90,7 +92,23 @@ Targeting the full framework from .NET Core, self-contained deployment, and ASP.
9092

9193
![Choose options per platform](./media/azure-web-apps/choose-options-new-net-core.png)
9294

93-
## Enable client-side monitoring for .NET applications
95+
# [Node.js](#tab/nodejs)
96+
97+
From within your App Service web app under **Settings** > **select Application Insights** > **Enable**. Node.js agent based monitoring is currently in preview.
98+
99+
# [Java](#tab/java)
100+
101+
Java App Service based web applications do not currently support automatic agent/extension based monitoring. To enable monitoring for your Java application, you need to [manually instrument your application](https://docs.microsoft.com/azure/azure-monitor/app/java-get-started).
102+
103+
# [Python](#tab/python)
104+
105+
Python App Service based web applications do not currently support automatic agent/extension based monitoring. To enable monitoring for your Python application, you need to [manually instrument your application](https://docs.microsoft.com/azure/azure-monitor/app/opencensus-python).
106+
107+
---
108+
109+
## Enable client-side monitoring
110+
111+
# [.NET](#tab/net)
94112

95113
Client-side monitoring is opt-in for ASP.NET. To enable client-side monitoring:
96114

@@ -107,7 +125,7 @@ Client-side monitoring is opt-in for ASP.NET. To enable client-side monitoring:
107125

108126
To disable client-side monitoring either remove the associated key value pair from the Application settings, or set the value to false.
109127

110-
## Enable client-side monitoring for .NET Core applications
128+
# [.NET Core](#tab/netcore)
111129

112130
Client-side monitoring is **enabled by default** for .NET Core apps with **Recommended collection**, regardless of whether the app setting 'APPINSIGHTS_JAVASCRIPT_ENABLED' is present.
113131

@@ -124,6 +142,20 @@ If for some reason you would like to disable client-side monitoring:
124142

125143
![Screenshot of application settings UI](./media/azure-web-apps/appinsights-javascript-disabled.png)
126144

145+
# [Node.js](#tab/nodejs)
146+
147+
To enable client-side monitoring for your Node.js application, you need to [manually add the client-side JavaScript SDK to your application](https://docs.microsoft.com/azure/azure-monitor/app/javascript).
148+
149+
# [Java](#tab/java)
150+
151+
To enable client-side monitoring for your Java application, you need to [manually add the client-side JavaScript SDK to your application](https://docs.microsoft.com/azure/azure-monitor/app/javascript).
152+
153+
# [Python](#tab/python)
154+
155+
To enable client-side monitoring for your Python application, you need to [manually add the client-side JavaScript SDK to your application](https://docs.microsoft.com/azure/azure-monitor/app/javascript).
156+
157+
---
158+
127159
## Automate monitoring
128160

129161
In order to enable telemetry collection with Application Insights, only the Application settings need to be set:
@@ -318,7 +350,7 @@ If the upgrade is done from a version prior to 2.5.1, check that the Application
318350
Below is our step-by-step troubleshooting guide for extension/agent based monitoring for .NET and .NET Core based applications running on Azure App Services.
319351

320352
> [!NOTE]
321-
> 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.
353+
> Java applications are only supported on Azure App Services via manual SDK based instrumentation and therefore the steps below do not apply to these scenarios.
322354
323355
1. Check that the application is monitored via `ApplicationInsightsAgent`.
324356
* Check that `ApplicationInsightsAgent_EXTENSION_VERSION` app setting is set to a value of "~2".

0 commit comments

Comments
 (0)