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: support/azure/app-service/app-service-web-nodejs-best-practices-troubleshoot-guide.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ ms.service: azure-app-service
12
12
---
13
13
# Best practices and troubleshooting guide for node applications on Azure App Service Windows
14
14
15
-
In this article, you learn best practices and troubleshooting steps for [Windows Node.js applications](quickstart-nodejs.md?pivots=platform-windows) running on Azure App Service (with [iisnode](https://github.com/azure/iisnode)).
15
+
In this article, you learn best practices and troubleshooting steps for [Windows Node.js applications](/azure/app-service/quickstart-nodejs?pivots=platform-windows) running on Azure App Service (with [iisnode](https://github.com/azure/iisnode)).
16
16
17
17
> [!WARNING]
18
18
> Use caution when using troubleshooting steps on your production site. Recommendation is to troubleshoot your app on a non-production setup for example your staging slot and when the issue is fixed, swap your staging slot with your production slot.
@@ -135,7 +135,7 @@ let keepaliveAgent = new Agent({
135
135
136
136
#### My node application is consuming too much CPU
137
137
138
-
You may receive a recommendation from Azure App Service on your portal about high cpu consumption. You can also set up monitors to watch for certain [metrics](web-sites-monitor.md). When checking the CPU usage on the [Azure portal Dashboard](/azure/azure-monitor/essentials/metrics-charts), check the MAX values for CPU so you don’t miss the peak values.
138
+
You may receive a recommendation from Azure App Service on your portal about high cpu consumption. You can also set up monitors to watch for certain [metrics](/azure/app-service/web-sites-monitor). When checking the CPU usage on the [Azure portal Dashboard](/azure/azure-monitor/essentials/metrics-charts), check the MAX values for CPU so you don’t miss the peak values.
139
139
If you believe your application is consuming too much CPU and you cannot explain why, you can profile your node application to find out.
140
140
141
141
#### Profiling your node application on Azure App Service with V8-Profiler
@@ -208,7 +208,7 @@ You can see that 95% of the time was consumed by the WriteConsoleLog function. T
208
208
209
209
### My node application is consuming too much memory
210
210
211
-
If your application is consuming too much memory, you see a notice from Azure App Service on your portal about high memory consumption. You can set up monitors to watch for certain [metrics](web-sites-monitor.md). When checking the memory usage on the [Azure portal Dashboard](/azure/azure-monitor/essentials/metrics-charts), be sure to check the MAX values for memory so you don’t miss the peak values.
211
+
If your application is consuming too much memory, you see a notice from Azure App Service on your portal about high memory consumption. You can set up monitors to watch for certain [metrics](/azure/app-service/web-sites-monitor). When checking the memory usage on the [Azure portal Dashboard](/azure/azure-monitor/essentials/metrics-charts), be sure to check the MAX values for memory so you don’t miss the peak values.
212
212
213
213
#### Leak detection and Heap Diff for Node.js
214
214
@@ -267,11 +267,11 @@ NODE.exe has a setting called `NODE_PENDING_PIPE_INSTANCES`. On Azure App Servic
267
267
268
268
Follow these links to learn more about Node.js applications on Azure App Service.
269
269
270
-
*[Get started with Node.js web apps in Azure App Service](quickstart-nodejs.md)
270
+
*[Get started with Node.js web apps in Azure App Service](/azure/app-service/quickstart-nodejs)
271
271
*[How to debug a Node.js web app in Azure App Service](/archive/blogs/azureossds/debugging-node-js-apps-on-azure-app-services)
272
272
*[Using Node.js Modules with Azure applications](/training/modules/create-nodejs-project-dependencies/)
273
273
*[Azure App Service Web Apps: Node.js](/archive/blogs/silverlining/windows-azure-websites-node-js)
0 commit comments