This topic describes the common metrics that are used to query and analyze logs collected by Log Service in WAF. You can use these metrics to configure alerts so that you can monitor exceptions in your workload as needed. This topic also provides the recommended alert thresholds of metrics and suggestions on handling metric exceptions.
|200||The server has processed the request and returned the requested data.||Before you initialize your workloads, set the alert threshold to 90% for status code 200. You can adjust the threshold as needed.||If the percentage of code 200 is lower than the specified threshold, identify the reason. For example, this metric may have decreased because the percentage of another status code has increased.|
|request_time_msec||Time period between the time when the client sends a request and the time when the client receives a response.||Set the alert thresholds based on the time required for actual service requests.||If it takes a long time to receive responses from a domain name, check the network connectivity between the client and WAF and that between WAF and the origin servers, and make sure that the origin servers respond properly.|
|upstream_response_time||The time period between the time when WAF sends data to the origin server and the time when WAF receives a response from the origin server.|
|ssl_handshake_time||The time required for an SSL handshake between the client and WAF during an HTTPS request.|
|status:302 and block_action:tmd/status:200 and block_action:tmd||The status code indicates whether CAPTCHA is triggered. Code 302 indicates that CAPTCHA is triggered, and code 200 indicates that CAPTCHA is not triggered and the user needs to customize HTTP flood protection.||When you initialize your workloads, we recommend that you set the alert thresholds for status code percentage to a value from 5% to 10%. You can adjust the thresholds based on the traffic blocked by WAF.||
|200 and block_action:antifraud||A request is blocked by data risk control.||Test the alert rule before you apply it. If you receive this alert frequently, contact us to adjust the alert threshold.|
|status:404||The server cannot find the requested resources.||Query the source IP addresses that trigger the alert.
|status:405||A request is blocked by either web application protection rules or HTTP ACL policy rules.||Use the log search feature to analyze the blocked request and the rule used to block the request, and find out whether this is a false positive.|
|status:444||A request is blocked by custom HTTP flood protection rules.||
|status:499||After a client sends a request, the server does not return data. After the maximum wait time of the client is reached, the client disconnects, and the server returns this status code.||
|status:500||A request cannot be processed due to the 500 Internal Server Error.||We recommend that you check the loads and database status of the origin server.|
|status:502||The server is used as a gateway or a proxy and receives invalid responses from the upstream server due to a 502 Bad Gateway error. The origin server does not respond due to low quality performance of the back-to-origin network or the fact that back-to-origin requests are blocked by access control policies configured for the origin server.||
|status:503||The service is unavailable due to overloads or maintenance needs.||Check for exceptions on the origin server.|
|status:504||The server serves as a gateway or proxy and fails to receive requests from the upstream server in time. The 504 Gateway Timeout error occurred.||Possible causes include: