Skip to content

Commit 5b1d647

Browse files
authored
updating to 60 second log collection time
1 parent ecbf45a commit 5b1d647

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/application-gateway/application-gateway-faq.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -348,11 +348,11 @@ Currently, one instance of Ingress Controller can only be associated to one Appl
348348

349349
Application Gateway provides three logs:
350350

351-
* **ApplicationGatewayAccessLog**: The access log contains each request submitted to the application gateway frontend. The data includes the caller's IP, URL requested, response latency, return code, and bytes in and out. The access log is collected every 300 seconds. It contains one record per application gateway.
351+
* **ApplicationGatewayAccessLog**: The access log contains each request submitted to the application gateway frontend. The data includes the caller's IP, URL requested, response latency, return code, and bytes in and out. It contains one record per application gateway.
352352
* **ApplicationGatewayPerformanceLog**: The performance log captures performance information for each application gateway. Information includes the throughput in bytes, total requests served, failed request count, and healthy and unhealthy backend instance count.
353353
* **ApplicationGatewayFirewallLog**: For application gateways that you configure with WAF, the firewall log contains requests that are logged through either detection mode or prevention mode.
354354

355-
For more information, see [Backend health, diagnostics logs, and metrics for Application Gateway](application-gateway-diagnostics.md).
355+
All logs are collected every 60 seconds. For more information, see [Backend health, diagnostics logs, and metrics for Application Gateway](application-gateway-diagnostics.md).
356356

357357
### How do I know if my backend pool members are healthy?
358358

0 commit comments

Comments
 (0)