在線上事故排查期間,僅靠肉眼掃視原始反向代理日誌,很難將用戶端速率限制激增(429)或用戶端提早中斷連線(499)與真正的上游服務崩潰(502 與 504)區分開來。內建的日誌擷取器可在瀏覽器本機掃描貼上的日誌行或拖入的 .log 檔案,精準分離出引號請求行之後的 HTTP 回應狀態碼標記或 JSON 狀態鍵值,並計算出精確的頻率分佈明細。
以下是一段來自發生延遲飆升的 API 閘道器的 Nginx Combined 格式混合日誌範例:
198.51.100.42 - - [01/Nov/2026:14:22:01 +0000] "GET /v2/orders?limit=50 HTTP/2.0" 200 4812 "-" "curl/8.7.1"
198.51.100.42 - - [01/Nov/2026:14:22:02 +0000] "POST /v2/orders HTTP/2.0" 308 0 "-" "curl/8.7.1"
203.0.113.19 - - [01/Nov/2026:14:22:03 +0000] "POST /v2/orders/ HTTP/2.0" 429 118 "-" "python-httpx/0.27.0"
192.0.2.88 - - [01/Nov/2026:14:22:05 +0000] "GET /v2/reports/export HTTP/2.0" 499 0 "-" "Mozilla/5.0"
192.0.2.88 - - [01/Nov/2026:14:22:09 +0000] "GET /v2/reports/export HTTP/2.0" 504 569 "-" "Mozilla/5.0"
203.0.113.55 - - [01/Nov/2026:14:22:10 +0000] "GET /v2/inventory HTTP/2.0" 200 1940 "-" "Go-http-client/2.0"
擷取器會同時彙總個別狀態碼與 RFC 9110 回應類別,協助您立即評估 SLI 錯誤預算消耗情況:
{
"totalResponses": 6,
"byClass": {
"2xx": { "count": 2, "share": "33.33%" },
"3xx": { "count": 1, "share": "16.67%" },
"4xx": { "count": 2, "share": "33.33%" },
"5xx": { "count": 1, "share": "16.67%" }
},
"byCode": [
{ "code": 200, "phrase": "OK", "count": 2, "standard": "RFC 9110" },
{ "code": 308, "phrase": "Permanent Redirect", "count": 1, "standard": "RFC 9110" },
{ "code": 429, "phrase": "Too Many Requests", "count": 1, "standard": "RFC 6585" },
{ "code": 499, "phrase": "Client Closed Request", "count": 1, "standard": "Nginx Extension" },
{ "code": 504, "phrase": "Gateway Timeout", "count": 1, "standard": "RFC 9110" }
]
}
對照 /v2/reports/export 路徑上成對出現的 499 與 504,可以立即看出故障模式:失去耐心的用戶端在上游工作程序回應前主動中斷了連線(499),而持續保持連線超過 proxy_read_timeout 門檻的請求則以 504 Gateway Timeout 終止。