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/app-service/troubleshoot-diagnostic-logs.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ Azure provides built-in diagnostics to assist with debugging an [App Service app
25
25
This article uses the [Azure portal](https://portal.azure.com) and Azure CLI to work with diagnostic logs. For information on working with diagnostic logs using Visual Studio, see [Troubleshooting Azure in Visual Studio](troubleshoot-dotnet-visual-studio.md).
26
26
27
27
> [!NOTE]
28
-
> In addition to the logging instructions in this article, there's new, integrated logging capability with Azure Monitor. You'll find more on this capability in the [Send logs to Azure Monitor](#send-logs-to-azure-monitor) section.
28
+
> In addition to the logging instructions in this article, you can also use the Azure Monitor integrated logging capability. You'll find more on this capability in the [Send logs to Azure Monitor](#send-logs-to-azure-monitor) section.
29
29
>
30
30
31
31
|Type|Platform|Log storage location|Description|
@@ -116,7 +116,7 @@ To save the error page or failed request tracing for Windows apps in the [Azure
116
116
117
117
Under **Detailed Error Logging** or **Failed Request Tracing**, select **On**, and then select **Save**.
118
118
119
-
Both types of logs are stored in the App Service file system. Up to 50 errors (files/folders) are retained. When the number of HTML files exceeds 50, the oldest error files are automatically deleted.
119
+
Both types of logs are stored in the App Service file system. Up to 50 errors (files or folders) are retained. When the number of HTML files exceeds 50, the oldest error files are automatically deleted.
120
120
121
121
The Failed Request Tracing feature by default captures a log of requests that failed with HTTP status codes between 400 and 600. To specify custom rules, you can override the `<traceFailedRequests>` section in the *web.config* file.
122
122
@@ -205,6 +205,6 @@ For Diagnostic Settings restrictions, refer to the [official Diagnostic Settings
205
205
206
206
## <a name="nextsteps"></a> Next steps
207
207
* [Query logs with Azure Monitor](../azure-monitor/logs/log-query-overview.md)
208
-
* [How to Monitor Azure App Service](web-sites-monitor.md)
208
+
* [How to Monitor Azure App Service](monitor-app-service.md)
209
209
* [Troubleshooting Azure App Service in Visual Studio](troubleshoot-dotnet-visual-studio.md)
210
210
* [Tutorial: Run a load test to identify performance bottlenecks in a web app](../load-testing/tutorial-identify-bottlenecks-azure-portal.md)
0 commit comments