Skip to content

Commit dbd305b

Browse files
Further updates
1 parent 1b5873e commit dbd305b

4 files changed

Lines changed: 3 additions & 3 deletions

File tree

support/azure/app-service/media/app-service-web-troubleshoot-HTTP-502-503/1-monitor-metrics.png renamed to support/azure/app-service/media/web-troubleshoot-http-502-503/1-monitor-metrics.png

File renamed without changes.

support/azure/app-service/media/app-service-web-troubleshoot-HTTP-502-503/2-restart.png renamed to support/azure/app-service/media/web-troubleshoot-http-502-503/2-restart.png

File renamed without changes.

support/azure/app-service/toc.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@
3131
- name: FAQs about scaling web apps
3232
href: ./scaling-web-app-faq.yml
3333
- name: Fix HTTP 502 and HTTP 503 Errors
34-
href: troubleshoot-http-502-http-503
34+
href: troubleshoot-http-502-http-503.md
3535
- name: Map your own custom domain
3636
href: /azure/app-service/app-service-web-tutorial-custom-domain
3737
- name: Node.js Best Practices and Troubleshooting Guide

support/azure/app-service/troubleshoot-http-502-http-503.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ Some of the metrics that you might want to monitor for your app are:
5454
- Memory working set
5555
- Requests
5656

57-
:::image type="content" source="./media/app-service-web-troubleshoot-HTTP-502-503/1-monitor-metrics.png" alt-text="Screenshot that shows metric options for an app in the portal." lightbox="./media/app-service-web-troubleshoot-HTTP-502-503/1-monitor-metrics.png":::
57+
:::image type="content" source="./media/web-troubleshoot-http-502-503/1-monitor-metrics.png" alt-text="Screenshot that shows metric options for an app in the portal." lightbox="./media/web-troubleshoot-http-502-503/1-monitor-metrics.png":::
5858

5959
For more information, see:
6060

@@ -124,7 +124,7 @@ For more information, see [Azure App Service diagnostics overview](/azure/app-se
124124

125125
Restarting your app is often the simplest way to recover from one-time problems. On the [Azure portal](https://portal.azure.com/) page for your app, you can stop or restart your app.
126126

127-
:::image type="content" source="./media/app-service-web-troubleshoot-HTTP-502-503/2-restart.png" alt-text="Screenshot that shows options for stopping and restarting an app in the portal.":::
127+
:::image type="content" source="./media/web-troubleshoot-http-502-503/2-restart.png" alt-text="Screenshot that shows options for stopping and restarting an app in the portal.":::
128128

129129
You can also manage your app by using Azure PowerShell. For more information, see
130130
[Manage Azure resources by using Azure PowerShell](/azure/azure-resource-manager/management/manage-resources-powershell).

0 commit comments

Comments
 (0)