All Products
Search
Document Center

Anti-DDoS:Fields included in full logs

Last Updated:Mar 31, 2026

Anti-DDoS Proxy records each HTTP request as a structured log entry. This page describes every field in the full log, including its description and an example value.

Basic information

FieldDescriptionExample
__topic__Log category. Always ddos_access_log.ddos_access_log
user_idAlibaba Cloud account ID.166688437215****

HTTP requests

FieldDescriptionExample
body_bytes_sentSize of the response body, in bytes.2
content_typeContent type of the response body.application/x-www-form-urlencoded
hostRequested domain name.api.aliyundoc.com
http_cookieCookie sent with the request.k1=v1;k2=v2
http_refererReferer header of the request. Returns - if the header is absent.http://aliyundoc.com
http_user_agentUser agent string of the request.Dalvik/2.1.0 (Linux; U; Android 10; Android SDK built for x86 Build/QSR1.200715.002)
http_x_forwarded_forIP address of the upstream proxy.192.0.XX.XX
httpsWhether the request uses HTTPS. Valid values: true, false.true
matched_hostDomain name matched by Anti-DDoS Proxy, which can be a wildcard domain. Returns - if no domain is matched.*.aliyundoc.com
real_client_ipOriginating IP address of the client. Returns - if the address cannot be retrieved.192.0.XX.XX
isp_lineInternet service provider (ISP) line, such as Border Gateway Protocol (BGP), China Telecom, or China Unicom.China Telecom
remote_addrIP address from which the request is initiated.192.0.XX.XX
remote_portPort of the immediate request sender.23713
src_ipIP address from which the request is initiated.192.0.XX.XX
src_portID of the port from which the request is initiated.23713
request_lengthSize of the request, in bytes.123
request_methodHTTP method of the request.GET
start_timeTime when Anti-DDoS Proxy returns the response to the client, as a Unix timestamp.1735553169000
request_time_msecTotal time for Anti-DDoS Proxy to receive the request, process it, and return the response, in milliseconds.44
request_uriURI of the request./answers/377971214/banner
server_nameName of the matched origin server. Returns default if no origin server is matched.api.aliyundoc.com
statusHTTP status code of the response.200
timeTime when the request is initiated, in ISO 8601 format.2024-12-30T18:06:09+08:00
querystringQuery string of the request.token=bbcd&abc=123
upstream_addrComma-separated list of origin server addresses, each in IP:Port format.192.0.XX.XX:443
upstream_ipIP address of the origin server.192.0.XX.XX
upstream_response_timeResponse time of the back-to-origin request, in seconds.
Note

If the famax engine (previous version) is used, the unit is milliseconds.

0.044
upstream_statusHTTP status code of the back-to-origin request.200
vip_addrIP address of the Anti-DDoS Proxy instance.203.107.XX.XX
http2_client_fingerprintRaw HTTP/2 client fingerprint.2:0;4:2097152;3:100|10485760|0|m,s,p,a
http2_client_fingerprint_md5MD5 hash (128-bit, 32 characters) derived from the raw HTTP/2 fingerprint. Used to identify and distinguish clients for analysis.ad8424af1cc590e09f7b0c499bf7fcdb
ssl_client_ja3_fingerprintingRaw JA3 fingerprint of the TLS client, derived from TLS handshake parameters including TLS version, cipher suites, compression algorithms, and TLS extensions.771,4865-49195-49196-49197,29,0
ssl_client_ja3_fingerprinting_md5MD5 hash derived from the raw JA3 fingerprint.c1bd7c674bbec9f0f2474e3eee3564f4
ssl_client_ja4_fingerprintingRaw JA4 fingerprint of the TLS client, derived from TLS handshake parameters including TLS version, cipher suites, compression algorithms, TLS extensions, browser version, and operating system.t13d1516h2_acb858a92679_e5627efa2ab1
ssl_client_ja4_fingerprinting_md5MD5 hash derived from the raw JA4 fingerprint.8c3d99fb6ed08a39c799aad27b4854f4
ssl_client_tls_fingerprinting_md5MD5 hash derived from the client TLS fingerprint.21d696a76962c9912d765a9372d8c773
cache_statusWhether the request hits the Anti-DDoS Proxy cache. Valid values: hit (found in cache), miss (not found in cache).hit
traceidGlobally unique identifier (GUID) assigned to each request in a distributed system. Persists through the entire request lifecycle and links log entries across services, enabling traceability and performance analysis.ac11000117388144519311412e387f

Client information

FieldDescriptionExample
ua_browserBrowser identifier.
Note

In some cases, a log does not contain this field.

ie9
ua_browser_familyBrowser series.
Note

In some cases, a log does not contain this field.

internet explorer
ua_browser_typeBrowser type.
Note

In some cases, a log does not contain this field.

web_browser
ua_browser_versionBrowser version.
Note

In some cases, a log does not contain this field.

9.0
ua_device_typeClient device type.
Note

In some cases, a log does not contain this field.

computer
ua_osOperating system identifier.
Note

In some cases, a log does not contain this field.

windows_7
ua_os_familyOperating system series.
Note

In some cases, a log does not contain this field.

windows
server_protocolProtocol and version returned by the origin server in response to back-to-origin requests.HTTP/1.1
ssl_protocolSSL or TLS protocol version used in the request.TLSv1.2
ssl_cipherCipher suite used in the request.ECDHE-RSA-AES128-GCM-SHA256
ssl_handshake_timeDuration of the TLS handshake initiated by the client, in milliseconds.99

Mitigation settings

FieldDescriptionExample
cc_actionAction taken by an HTTP flood mitigation rule. See cc_action values.accept
cc_blocksWhether the request is blocked by an HTTP flood mitigation rule. 1 means blocked; any other value means allowed. If this field is absent, last_result records the outcome instead.1
cc_phaseMitigation feature that processed the request. Values differ by engine version. See cc_phase values.gfbwip
last_moduleMitigation feature that made the final decision for the request. See last_module values.gfareaban
last_ownerName of the rule that made the final decision. Anti-DDoS Proxy rule naming conventions: names starting with smartcc_ belong to intelligent protection rules, names starting with global belong to DDoS mitigation policy rules, and names starting with gf_internal belong to HTTP flood mitigation rules.global_th_4_C_****
last_resultFinal action taken on the request. ok means allowed; failed means not allowed (blocked or CAPTCHA verification failed). If this field is absent, cc_blocks records the outcome instead.failed

cc_action values

ValueDescription
acceptThe request is allowed.
blockThe request is blocked.
challengeCAPTCHA verification is triggered to verify the source IP address.
alarmThe request is recorded in logs and allowed.

cc_phase values

The value depends on which engine version your Anti-DDoS Proxy instance uses.

Tengine engine

ValueFeature
gfbwipBlacklist and whitelist
gfccHTTP flood mitigation
gfaclCustom mitigation policy
gfglobalDDoS mitigation policy
gfareabanLocation blacklist

Famax engine

ValueFeature
ipFilterBlacklist and whitelist
statProtectHTTP flood mitigation
preciseProtectCustom mitigation policy
regionBLockLocation blacklist

last_module values

ValueFeature
gfareabanLocation blacklist
gfbwipBlacklist and whitelist
gfaclAccurate access control
gfccHTTP flood mitigation
gfglobalDDoS mitigation policy