EdgeOne nodes respond to most of the user requests. To facilitate access analysis, EdgeOne packages access logs of the entire network at an hourly granularity and retains them for 30 days by default. These logs can also be downloaded.
Currently, only node access logs of sites accelerated are provided.
Log in to the EdgeOne console. Click Log Service > Offline Logs on the left sidebar.
On the offline logs page, select the logs of a site or a subdomain name. You can also filter offline logs by time.
- The access logs are packed every hour by default. If the selected domain name is not requested during one hour, no log pack will be generated for this hour.
- Each log pack is compressed to a GZ file.
- Offline logs are stored and queried in UTC+00:00 by default.
- Offline logs are collected from each EdgeOne node, so the delay may vary. Generally, querying and downloading of log packs can be delayed by about 30 minutes. Log packs will be added continuously and will stabilize after 2-3 hours.
Logs are stored in JSON format by default. The log fields are described as follows:
When a field is not specified:
-if the field has no data.
-1if the field has no data.
|RequestID||String||Unique ID of the client request|
|RequestTime||int||Client request time, which is displayed in UTC+00:00 in the RFC 3339 standard format|
|RequestHost||string||Client request host|
|RequestBytes||int||Client request size, which includes the size of the file itself and request headers|
|RequestMethod||string||HTTP client request method|
|RequestUrl||string||Client request URL|
|RequestUrlQueryString||string||A query string that is carried in the client request URL|
|RequestUA||string||Client request User-Agent|
|RequestRange||string||Client request Range|
|RequestReferer||string||Client request Referer|
|RequestProtocol||string||Client request HTTP protocol: HTTP, HTTPS, and HTTP/3|
|RemotePort||int||Port connecting the client and nodes under the TCP protocol. This field will be "-" if the port does not exist.|
|EdgeCacheStatus||string||Whether the client request hits the node cache: HIT, MISS, and Dynamic|
|EdgeResponseStatusCode||int||Response status code returned to the client by the nodes|
|EdgeResponseBytes||int||Response size returned to the client by the nodes|