Skip to content

Commit 20943fe

Browse files
More updates
1 parent 2656d5d commit 20943fe

5 files changed

Lines changed: 7 additions & 7 deletions

support/azure/app-service/app-service-web-nodejs-best-practices-troubleshoot-guide.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.service: azure-app-service
1212
---
1313
# Best practices and troubleshooting guide for node applications on Azure App Service Windows
1414

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)).
1616

1717
> [!WARNING]
1818
> 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({
135135
136136
#### My node application is consuming too much CPU
137137

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.
139139
If you believe your application is consuming too much CPU and you cannot explain why, you can profile your node application to find out.
140140

141141
#### 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
208208

209209
### My node application is consuming too much memory
210210

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.
212212

213213
#### Leak detection and Heap Diff for Node.js
214214

@@ -267,11 +267,11 @@ NODE.exe has a setting called `NODE_PENDING_PIPE_INSTANCES`. On Azure App Servic
267267

268268
Follow these links to learn more about Node.js applications on Azure App Service.
269269

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)
271271
* [How to debug a Node.js web app in Azure App Service](/archive/blogs/azureossds/debugging-node-js-apps-on-azure-app-services)
272272
* [Using Node.js Modules with Azure applications](/training/modules/create-nodejs-project-dependencies/)
273273
* [Azure App Service Web Apps: Node.js](/archive/blogs/silverlining/windows-azure-websites-node-js)
274-
* [Node.js Developer Center](../nodejs-use-node-modules-azure-apps.md)
274+
* [Node.js Developer Center](/azure/nodejs-use-node-modules-azure-apps)
275275
* [Exploring the Super Secret Kudu Debug Console](https://www.youtube.com/watch?v=-VjqyvA2XjM)
276276

277277

support/azure/app-service/toc.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,8 +10,6 @@
1010
href: ./connection-issues-with-ssl-or-tls/use-azure-app-service-certificate-with-application-gateway.md
1111
- name: Troubleshoot Azure App Service
1212
href: ./welcome-app-service.yml
13-
- name: Node.js Best Practices and Troubleshooting Guide
14-
href: app-service-web-nodejs-best-practices-troubleshoot-guide.md
1513
- name: Capture memory dumps in Azure App Service
1614
href: ./capture-memory-dumps-app-service.md
1715
- name: Create or delete web apps FAQs
@@ -34,6 +32,8 @@
3432
href: ./scaling-web-app-faq.yml
3533
- name: Map your own custom domain
3634
href: /azure/app-service/app-service-web-tutorial-custom-domain
35+
- name: Node.js Best Practices and Troubleshooting Guide
36+
href: app-service-web-nodejs-best-practices-troubleshoot-guide.md
3737
- name: Open-source technologies FAQs for Web Apps
3838
href: web-apps-open-source-technologies-faqs.md
3939
- name: Troubleshoot an app in Azure App Service using Visual Studio

support/azure/app-service/troubleshoot-instance-rela.md renamed to support/azure/app-service/troubleshoot-http-502-http-503.md

File renamed without changes.

support/azure/app-service/troubleshoot-instance-related-.md renamed to support/azure/app-service/troubleshoot-intermittent-outbound-connection-errors.md

File renamed without changes.

support/azure/app-service/troubleshoot-instance-related-issues-on-Azure.md renamed to support/azure/app-service/troubleshoot-performance-degradation.md

File renamed without changes.

0 commit comments

Comments
 (0)