Log Management

Log Description

Log file latency: You can query log files generated over the past six hours on the Logs page.

The log naming rules are as follows: Log time span-Acceleration domain name-Service area.gz. The service area is represented by a two letter abbreviation. Logs ending in cn are for areas in the Chinese mainland, and those ending in ov are for areas outside the Chinese mainland. So a typical log name might be 2018021123-www.example01.com-ov.gz.
By default, a log file is generated for each domain name every hour, and 24 log files are generated every day.

Example of log file content

[05/Feb/2018:07:54:52 +0800] x.x.x.x 1 "-" "HTTP/1.1" "GET" "www.test.com" "/test/1234.apk" 206 720 HIT "Mozilla/5.0 (Linux; U; Android 6.0; en-us; EVA-AL10 Build/HUAWEIEVA-AL10) AppleWebKit/533.1 (KHTML, like Gecko) Mobile Safari/533.1" "bytes=-256"

Table 1 describes each field (from left to right) in the log.

**Table 1** Log fields
No.	Field Description	Example
1	Log generation time	[05/Feb/2018:07:54:52 +0800]
2	Access IP address	x.x.x.x
3	Latency (ms)	1
4	Referer information	-
5	HTTP protocol identifier	HTTP/1.1
6	HTTP request method	GET
7	Acceleration domain name	www.test.com
8	Requested path	/test/1234.apk
9	HTTP status code	206
10	Response size (in bytes)	720
11	Cache hit status	HIT
12	User-Agent information, which helps servers recognize the OS, OS version, CPU, browser, and browser's version information	Mozilla/5.0 (Linux; U; Android 6.0; zh-cn; EVA-AL10 Build/HUAWEIEVA-AL10) AppleWebKit/533.1 (KHTML, like Gecko) Mobile Safari/533.1
13	Range information specifies the positions of the first and last bytes for the data to be returned. bytes can be expressed by the following three methods: bytes=x-y: requesting content from the xth to yth byte bytes=-y: requesting content from the last y bytes bytes=x-: requesting content from the xth to the last byte	bytes=-256