Skip to content

Commit b1bb173

Browse files
committed
updates
1 parent 62b7f32 commit b1bb173

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/app-service/troubleshoot-diagnostic-logs.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ Azure provides built-in diagnostics to assist with debugging an [App Service app
2525
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).
2626

2727
> [!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.
2929
>
3030
3131
|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
116116

117117
Under **Detailed Error Logging** or **Failed Request Tracing**, select **On**, and then select **Save**.
118118

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

121121
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.
122122

@@ -205,6 +205,6 @@ For Diagnostic Settings restrictions, refer to the [official Diagnostic Settings
205205
206206
## <a name="nextsteps"></a> Next steps
207207
* [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)
209209
* [Troubleshooting Azure App Service in Visual Studio](troubleshoot-dotnet-visual-studio.md)
210210
* [Tutorial: Run a load test to identify performance bottlenecks in a web app](../load-testing/tutorial-identify-bottlenecks-azure-portal.md)

0 commit comments

Comments
 (0)