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-nodejs.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,15 +10,15 @@ ms.reviewer: abinetabate
10
10
11
11
# Application Monitoring for Azure App Service and Node.js
12
12
13
-
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
+
Monitoring of your Node.js web applications running on [Azure App Services](../../app-service/index.yml)doesn't require any modifications to the code. This article walks you through enabling Azure Monitor Application Insights monitoring and provides preliminary guidance for automating the process for large-scale deployments.
14
14
15
15
## Enable Application Insights
16
16
17
17
The easiest way to enable application monitoring for Node.js applications running on Azure App Services is through Azure portal.
18
18
Turning on application monitoring in Azure portal will automatically instrument your application with Application Insights, and doesn't require any code changes.
19
19
20
20
> [!NOTE]
21
-
> If both auto-instrumentation monitoring and manual SDK-based instrumentation are 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.
21
+
> If both auto-instrumentation monitoring and manual SDK-based instrumentation are 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)in this article.
22
22
23
23
### Auto-instrumentation through Azure portal
24
24
@@ -39,7 +39,7 @@ The integration is in public preview. The integration adds Node.js SDK, which is
39
39
40
40
:::image type="content"source="./media/azure-web-apps/change-resource.png" alt-text="Screenshot of Change your resource dropdown.":::
41
41
42
-
3. Once you have specified which resource to use, you are all set to go.
42
+
3. Once you've specified which resource to use, you're all set to go.
43
43
44
44
:::image type="content"source="./media/azure-web-apps-nodejs/app-service-node.png" alt-text="Screenshot of instrument your application.":::
45
45
@@ -79,7 +79,7 @@ Below is our step-by-step troubleshooting guide for extension/agent based monito
79
79
80
80
- Confirm that the `Application Insights Extension Status` is `Pre-Installed Site Extension, version 2.8.x.xxxx, is running.`
81
81
82
-
If it is not running, follow the [enable Application Insights monitoring instructions](#enable-application-insights).
82
+
If it isn't running, follow the [enable Application Insights monitoring instructions](#enable-application-insights).
83
83
84
84
- Navigate to *D:\local\Temp\status.json* and open *status.json*.
0 commit comments