최신 업데이트:2026-01-27 11:03:19
This article provides an overview of CDN access logs within the platform’s native data, as well as detailed explanations of each log field.
| No. | Field Name | Field Code | Data Type | Field Description |
|---|---|---|---|---|
| 1 | Log Version | log_version | LONG | Used to indicate the version information of the log. |
| 2 | Log Sampling Rate | log_sampling_rate | INT | A value of N indicates that one real-time log entry will be generated for every N requests. |
| 3 | Content Code | content_code | STRING | An identifier used to classify different requests. It can be used for categorized reporting, billing, and request processing. |
| 4 | Acceleration Domain | hostname | STRING | The hostname on the acceleration platform configured to serve the request. If the acceleration domain is a wildcard domain, the log entry begins with a ‘.’. |
| 5 | Request ID | request_id | STRING | A unique identifier for the request, globally unique within the platform. Useful for debugging. |
| 6 | Log Timestamp (ms) | log_timestamp_ms | LONG | The timestamp in milliseconds when this log was generated. |
| No. | Field Name | Field Code | Data Type | Field Description |
|---|---|---|---|---|
| 1 | Real Client IP | client_real_ip | STRING | The real client IP. Preferentially taken from the Cdn-Src-Ip header; if unavailable, the value from remote-ip is used. |
| 2 | Real Client Port | client_real_port | INT | The real client port. Preferentially taken from the Cdn-Src-Port header; if unavailable, the value from remote-port is used. |
| 3 | Connection Client IP | client_ip | STRING | The client IP that establishes the TCP connection with the acceleration node. Obtained from remote-ip. |
| 4 | Connection Client Port | client_port | INT | The destination port used by the client for TCP connection to the acceleration node. Extracted from remote-port. |
| 5 | HTTP Authentication Username | client_remote_auth_user | STRING | The HTTP basic authentication username, extracted from the Authorization request header. |
| 6 | Real Client IP Version | client_ip_version | INT | The IP protocol version of the client IP. 4 indicates IPv4, and 6 indicates IPv6. |
| 7 | Real Client Continent | client_continent | STRING | The continent to which the client IP belongs. Supports both Chinese and English. |
| 8 | Real Client Country or Region | client_country | STRING | The country (e.g., United States, China, Russia) or region (e.g., Mainland China, Hong Kong, Macau, Taiwan) associated with the client IP. Supports code, Chinese, and English. For codes, the ISO 3166 two-letter standard is used. |
| 9 | Real Client Region (Province/State) | client_region | STRING | The region associated with the client IP, such as provinces in mainland China or states in the United States. Supports both code and Chinese. For codes, the ISO 3166 two-letter standard is used. |
| 10 | Real Client ISP | client_isp | STRING | The ISP to which the client IP belongs. Supports both Chinese and English. |
| 11 | Real Client Latitude | client_latitude | STRING | The latitude associated with the client IP. |
| 12 | Real Client Longitude | client_longitude | STRING | The longitude associated with the client IP. |
| 13 | Client User Agent | client_user_agent | STRING | The value of the User-Agent request header. |
| 14 | Client Browser Name | client_browser | STRING | The name of the client’s browser, extracted from the User-Agent header in the request. |
| 15 | Client Device Name | client_device | STRING | The name of the client’s device, extracted from the User-Agent header in the request. |
| 16 | Client Operating System Name | client_os | STRING | The name of the client’s operating system, extracted from the User-Agent header in the request. |
| No. | Field Name | Field Code | Data Type | Field Description |
|---|---|---|---|---|
| 1 | Request Start Time (ms) | request_timestamp_ms | LONG | The millisecond-level timestamp of the first byte of the client request received by the node, representing the start time of the request. |
| 2 | SNI Hostname | request_tls_server_name | STRING | The Server Name carried in the SNI of the TLS handshake packet requested by the client. |
| 3 | SSL Protocol Version | request_ssl_protocol | STRING | The SSL/TLS protocol version for the connection. Includes: SSLv3, TLSv1, TLSv1.1, TLSv1.2, TLSv1.3. |
| 4 | SSL Reuse Indicator | request_ssl_reuse | INT | Flag indicating whether the SSL/TLS session for the client request is reused. 1 means reused, 0 means not reused. |
| 5 | Request HOST | request_host | STRING | The value of the Host request header from the client. Note: If the request port is not 80 or 443, the port number will be included in this field. |
| 6 | HTTP Protocol Version | request_http_protocol | STRING | The HTTP protocol version used by the client request, e.g., HTTP/1.0, HTTP/1.1, HTTP/2.0, HTTP/3.0. |
| 7 | Request Protocol Scheme | request_scheme | STRING | The protocol scheme used in the client request, including: http, https. |
| 8 | Request Method | request_method | STRING | The HTTP method of the client request, e.g., GET, POST, PUT, DELETE, PATCH, HEAD, OPTION, etc. |
| 9 | Request URL | request_url | STRING | The complete URL requested by the client. |
| 10 | Request URL Full Query String | request_url_query_string | STRING | The complete set of query parameters attached to the request URL. Note: Does not start with a question mark. For example: deviceFamily=iPhone&domain=apps,books&storefrontId=143465&userId=16694213637. |
| 11 | Request URI Path | request_url_path | STRING | The requested URI path, excluding query parameters. Begins with ‘/’. |
| 12 | Request Header Referer | request_referer | STRING | The value of the Referer request header from the client. |
| 13 | Request Header Content-Type | request_content_type | STRING | The value of the Content-Type request header from the client request. |
| 14 | Request Header Range | request_range | STRING | The value of the Range request header from the client request. |
| 15 | Request Size | request_bytes | LONG | The traffic size of the request, including the request line, headers, and body. Unit: bytes. |
| 16 | Request Header Size | request_header_bytes | LONG | The traffic size of the request headers, including the request line and headers, excluding the body. Unit: bytes. |
| 17 | Request Delivery Rate | request_tcp_delivery_rate | LONG | The data transmission rate for this request as measured by the TCP stack. Unit: bytes/second. |
| 18 | Minimum Request RTT | request_tcp_min_rtt | LONG | The minimum RTT for this request as measured by the TCP stack. Unit: microseconds. |
| 19 | Average Request RTT | request_tcp_rtt | LONG | The average RTT for this request as measured by the TCP stack. Unit: microseconds. |
| 20 | First Request on TCP Connection | request_tcp_initial_request | INT | Indicates whether this request is the first one on the current TCP connection. 1 means it is the first request, 0 means it is not. |
| 21 | Request Receive Duration | request_receive_duration | DOUBLE | The time it takes to fully receive the client request, i.e., the duration from the node receiving the first byte of the client’s request to the point it is ready to process or forward it. Unit: seconds. |
| No. | Field Name | Field Code | Data Type | Field Description |
|---|---|---|---|---|
| 1 | Edge Server IP | edge_server_ip | STRING | Accelerated node server IP address. |
| 2 | Edge Server Country or Region | edge_server_country | STRING | Country (such as the United States, China, Russia, etc.) or region (such as Mainland China, Hong Kong, Macau, Taiwan, etc.) where the accelerated node server IP is located. Supports codes, Chinese, and English. The code data follows the ISO 3166 two-letter standard. |
| 3 | Edge Server Region (Province/State) | edge_server_region | STRING | Region where the accelerated node server IP is located. For example: provinces in Mainland China or states in the United States. Supports codes and Chinese. The code data follows the ISO 3166 two-letter standard. |
| 4 | Edge Server ISP | edge_server_isp | STRING | The ISP to which the accelerated node server IP belongs. Supports Chinese and English. |
| 5 | Edge Server Latitude | edge_server_latitude | STRING | Latitude where the accelerated node server IP is located. |
| 6 | Edge Server Longitude | edge_server_longitude | STRING | Longitude where the accelerated node server IP is located. |
| 7 | Edge Node Server Port | edge_server_port | INT | The server port of the acceleration node. |
| Number | Field Name | Field Code | Data Type | Field Description |
|---|---|---|---|---|
| 1 | Edge Node Cache Hit Status | cache_status_edge | STRING | This field indicates the cache hit status of the request at the edge node. MISS means the cache was not hit, and HIT means the cache was hit. |
| 2 | Cache Hit Status | cache_status | STRING | This field indicates the cache hit status of the request. MISS means the cache was not hit, and HIT means the cache was hit. Note that this status reflects the cache hit situation across the entire acceleration node chain. Therefore, if the status is MISS at the edge node but HIT at the relay node, it will be marked as HIT. |
| No. | Field Name | Field Code | Data Type | Field Description |
|---|---|---|---|---|
| 1 | Response Send Duration | response_send_duration | DOUBLE | Duration of sending the complete response, i.e., the time the node takes to send the entire response body (until the last byte) to the system buffer. Unit: seconds. |
| 2 | Node Response Status Code | response_status_code | LONG | HTTP status code sent by the acceleration node server to the client. For example: 200, 302, 403, 500, etc. |
| 3 | Response Size | response_bytes | LONG | The amount of traffic sent by the acceleration node server to the client, including both response headers and response body. Unit: bytes. |
| 4 | Response Body Size | response_body_bytes | LONG | Traffic size of the response body sent by the acceleration node server to the client, excluding response headers. Unit: bytes. |
| 5 | Response Header Content-Type | response_content_type | STRING | The value of the Content-Type response header sent by the acceleration node server to the client. |
| 6 | Response Header Content-Length | response_content_length | STRING | The value of the Content-Length response header sent by the acceleration node server to the client. |
| 7 | Response Header Via | response_via | STRING | The value of the Via response header sent by the acceleration node server to the client. |
| 8 | Response Initiation Indicator | response_first_byte_sent | INT | Indicates whether the first byte of the response body for the current request has been sent to the client. A value of 1 means it has been sent (response started), and 0 means it has not. - For 200 responses, the value becomes 1 after the response header is sent. - For 206 responses, if the Range header in the request starts with ‘0’, the value is 1 after the response header is sent. - If there is no response body, the value is 1 after the response header is sent. |
| 9 | Response Completion Indicator | response_last_byte_sent | INT | Indicates whether the last byte of the response body for the current request has been sent to the client. A value of 1 means the last byte has been sent (response complete), and 0 means it has not. - Under normal transfer conditions, if all data has been sent to the client, the value is 1; otherwise, it is 0. - For Chunked Transfer Encoding, if the last chunk has been successfully sent to the client, the value is 1. |
| 10 | Response Time (ms) | response_time_ms | LONG | The total duration of request processing, measured from the time the acceleration node server reads the first byte from the client to the time it sends the last byte back to the client. This includes both the request receive time and the response processing time. For persistent connection range requests, this field represents the processing time for each individual range request. Unit: milliseconds. |
| No. | Field Name | Field Code | Data Type | Field Description |
|---|---|---|---|---|
| 1 | Custom Log Field | custom_field | STRING | If the standard log fields do not meet your logging requirements, you can configure custom log fields on the acceleration domain. Custom logs are output in Key-Value format, with multiple KV pairs separated by commas. |
Note:
- The availability of log fields may vary depending on the actual configuration. We recommend selecting them according to your specific business requirements.
- Currently, logs related to live streaming services are not included.