You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-monitor/app/azure-web-apps-java.md
+16-17Lines changed: 16 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,19 +9,19 @@ ms.custom: "devx-track-java"
9
9
10
10
# Application Monitoring for Azure App Service and Java
11
11
12
-
Monitoring of your Java-based web applications running on [Azure App Services](../../app-service/index.yml) does not require any modifications to the code. 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.
12
+
Monitoring of your Java web applications running on [Azure App Services](../../app-service/index.yml) does not require any modifications to the code. 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.
13
13
14
14
## Enable Application Insights
15
15
16
-
The recommended way to enable application monitoring for Java application running on Azure App Services is through Azure portal. Turning on application monitoring in Azure portal will automatically instrument your application with application insights.
16
+
The recommended way to enable application monitoring for Java applications running on Azure App Services is through Azure portal.
17
+
Turning on application monitoring in Azure portal will automatically instrument your application with Application Insights, and doesn't require any code changes.
18
+
You can apply additional configurations, and then based on your specific scenario you [add your own custom telemetry](./java-in-process-agent.md#modify-telemetry) if needed.
17
19
18
20
### Auto-instrumentation through Azure portal
19
21
20
-
This method requires no code change or advanced configurations, making it the easiest way to get started with monitoring for Azure App Services. You can apply additional configurations, and then based on your specific scenario you can evaluate whether more advanced monitoring through [manual instrumentation](./java-2x-get-started.md?tabs=maven) is needed.
21
-
22
-
### Enable backend monitoring
23
-
24
-
You can turn on monitoring for your Java apps running in Azure App Service just with one click, no code change required. Application Insights for Java is integrated with App Service on Linux - both code-based and custom containers, and with App Service on Windows - code-based apps. It is important to know how your application will be monitored. The integration adds [Application Insights Java 3.x](./java-in-process-agent.md) and you will get the telemetry auto-collected.
22
+
You can turn on monitoring for your Java apps running in Azure App Service just with one click, no code change required.
23
+
Application Insights for Java is integrated with Azure App Service on Linux - both code-based and custom containers, and with App Service on Windows for code-based apps.
24
+
The integration adds [Application Insights Java 3.x](./java-in-process-agent.md) and you will get the telemetry auto-collected.
25
25
26
26
1.**Select Application Insights** in the Azure control panel for your app service, then select **Enable**.
27
27
@@ -32,9 +32,9 @@ You can turn on monitoring for your Java apps running in Azure App Service just
32
32
> [!NOTE]
33
33
> When you select **OK** to create the new resource you will be prompted to **Apply monitoring settings**. Selecting **Continue** will link your new Application Insights resource to your app service, doing so will also **trigger a restart of your app service**.
34
34
35
-
:::image type="content"source="./media/azure-web-apps/change-resource.png" alt-text="Screenshot of Change your resource dropdown.":::
35
+
:::image type="content"source="./media/azure-web-apps/change-resource.png" alt-text="Screenshot of Change your resource dropdown.":::
36
36
37
-
3. This step is not required. After specifying which resource to use, you can configure the Java agent. If you do not configure the Java agent, default configurations will apply.
37
+
3. This last step is optional. After specifying which resource to use, you can configure the Java agent. If you do not configure the Java agent, default configurations will apply.
38
38
39
39
The full [set of configurations](./java-standalone-config.md) is available, you just need to paste a valid [json file](./java-standalone-config.md#an-example). **Exclude the connection string and any configurations that are in preview** - you will be able to add the items that are currently in preview as they become generally available.
40
40
@@ -49,17 +49,16 @@ To enable client-side monitoring for your Java application, you need to [manuall
49
49
50
50
## Automate monitoring
51
51
52
-
### Application settings
53
-
54
52
In order to enable telemetry collection with Application Insights, only the following Application settings need to be set:
55
53
56
-
|App setting name | Definition | Value |
57
-
|-----------------|:------------|-------------:|
58
-
|ApplicationInsightsAgent_EXTENSION_VERSION | Controls runtime monitoring |`~2` for Windows or `~3` for Linux |
59
-
|XDT_MicrosoftApplicationInsights_Java | Flag to control that Java agent is included | 0 or 1 only applicable in Windows
60
-
|APPLICATIONINSIGHTS_SELF_DIAGNOSTICS_LEVEL | Only use it if you need to debug the integration of Application Insights with App Service | debug
54
+
:::image type="content"source="./media/azure-web-apps-java/application-settings-java.png" alt-text="Screenshot of App Service Application Settings with available Application Insights settings.":::
55
+
56
+
### Application settings definitions
61
57
62
-
:::image type="content"source="./media/azure-web-apps-java/application-settings-java.png" alt-text=" Screenshot of App Service Application Settings with available Application Insights settings.":::
58
+
| App setting name | Definition | Value |
59
+
|------------------|------------|------:|
60
+
| ApplicationInsightsAgent_EXTENSION_VERSION | Main extension, which controls runtime monitoring. |`~2` in Windows or `~3` in Linux. |
61
+
| XDT_MicrosoftApplicationInsights_Java | Flag to control if Java agent is included. | 0 or 1 (only applicable in Windows). |
63
62
64
63
> [!NOTE]
65
64
> Profiler and snapshot debugger are not available for Java applications
Copy file name to clipboardExpand all lines: articles/azure-monitor/app/azure-web-apps-nodejs.md
+25-18Lines changed: 25 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,28 +9,34 @@ ms.custom: "devx-track-js"
9
9
10
10
# Application Monitoring for Azure App Service and Node.js
11
11
12
-
Enabling monitoring on your Node.js 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.
12
+
Monitoring of your Node.js web applications running on [Azure App Services](../../app-service/index.yml) does not require any modifications to the code. 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.
13
+
14
+
## Enable Application Insights
15
+
16
+
The easiest way to enable application monitoring for Node.js applications running on Azure App Services is through Azure portal.
17
+
Turning on application monitoring in Azure portal will automatically instrument your application with Application Insights, and doesn't require any code changes.
13
18
14
19
> [!NOTE]
15
20
> 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.
16
21
17
-
##Enable agent-based monitoring
22
+
### Auto-instrumentation through Azure portal
18
23
19
-
You can monitor your Node.js apps running in Azure App Service without any code change, just with a couple of simple steps. Application insights for Node.js applications is integrated with App Service on Linux - both code-based and custom containers, and with App Service on Windows for code-based apps. The integration is in public preview. The integration adds Node.js SDK, which is in GA.
24
+
You can turn on monitoring for your Node.js apps running in Azure App Service just with one click, no code change required.
25
+
Application Insights for Node.js is integrated with Azure App Service on Linux - both code-based and custom containers, and with App Service on Windows for code-based apps.
26
+
The integration is in public preview. The integration adds Node.js SDK, which is in GA.
20
27
21
28
1.**Select Application Insights** in the Azure control panel for your app service, then select **Enable**.
22
29
23
30
:::image type="content"source="./media/azure-web-apps/enable.png" alt-text="Screenshot of Application Insights tab with enable selected.":::
24
31
25
32
2. Choose to create a new resource, or select an existing Application Insights resource for this application.
26
33
27
-
> [!NOTE]
28
-
> When you click**OK** to create the new resource you will be prompted to **Apply monitoring settings**. Selecting **Continue** will link your new Application Insights resource to your app service, doing so will also **trigger a restart of your app service**.
29
-
34
+
> [!NOTE]
35
+
> When you select**OK** to create the new resource you will be prompted to **Apply monitoring settings**. Selecting **Continue** will link your new Application Insights resource to your app service, doing so will also **trigger a restart of your app service**.
36
+
30
37
:::image type="content"source="./media/azure-web-apps/change-resource.png" alt-text="Screenshot of Change your resource dropdown.":::
31
-
32
-
3. Once you have specified which resource to use, you are all set to go.
33
38
39
+
3. Once you have specified which resource to use, you are all set to go.
34
40
35
41
:::image type="content"source="./media/azure-web-apps-nodejs/app-service-node.png" alt-text="Screenshot of instrument your application.":::
36
42
@@ -41,22 +47,22 @@ To enable client-side monitoring for your Node.js application, you need to [manu
41
47
42
48
## Automate monitoring
43
49
44
-
In order to enable telemetry collection with Application Insights, only the Application settings need to be set:
45
-
46
-
:::image type="content"source="./media/azure-web-apps-nodejs/application-settings-nodejs.png" alt-text="Screenshot ot App Service Application Settings with available Application Insights settings.":::
50
+
In order to enable telemetry collection with Application Insights, only the following Application settings need to be set:
47
51
52
+
:::image type="content"source="./media/azure-web-apps-nodejs/application-settings-nodejs.png" alt-text="Screenshot of App Service Application Settings with available Application Insights settings.":::
48
53
49
54
### Application settings definitions
50
55
51
-
|App setting name | Definition | Value |
52
-
|-----------------|:------------|-------------:|
53
-
|ApplicationInsightsAgent_EXTENSION_VERSION | Main extension, which controls runtime monitoring. |`~2` in Windows or `~3` in Linux |
54
-
|XDT_MicrosoftApplicationInsights_NodeJS |Flag to control if node.js Agent is included. | 0 or 1 only applicable in Windows. |
56
+
|App setting name | Definition | Value |
57
+
|------------------|------------|------:|
58
+
|ApplicationInsightsAgent_EXTENSION_VERSION | Main extension, which controls runtime monitoring. |`~2` in Windows or `~3` in Linux.|
59
+
|XDT_MicrosoftApplicationInsights_NodeJS | Flag to control if node.js agent is included. | 0 or 1 (only applicable in Windows). |
55
60
61
+
> [!NOTE]
62
+
> Profiler and snapshot debugger are not available for Node.js applications
0 commit comments