Observability
  • Log Service
    • Overview
    • Real-time Logs
      • Real-time Logs Overview
      • Push to Tencent Cloud CLS
      • Push to AWS S3-Compatible COS
      • Push to HTTP Server
    • Offline Logs
    • Related References
      • Field description
        • L7 Access Logs
        • L4 Proxy Logs
      • Real-Time Log Push Filter Conditions
      • Custom Log Push Fields
  • Data Analysis
    • Overview
    • Traffic Analysis
    • Cache Analysis
    • Security Analysis
      • Site Security Overview
      • Web Security Analysis
    • L4 Proxy
    • DNS Resolution
    • Related References
      • How to use filter condition
      • How to Modify Query Time Range
      • How to Export Statistical Data and Reports

Offline Logs

Feature Overview

To facilitate user access analysis by customers, EdgeOne packages access logs on an hourly basis, and provides download services.

Offline Log Format

Logs are stored in JSON Lines format by default. Each JSON line represents a single log.
Log packages are compressed in .gz format with gzip. Due to the directory system limitations in MacOS, double-click for decompression may cause an error. In this case, you can navigate to the directory containing the logs, and use the following Terminal command for decompression.
gunzip {your_file_name}.log

Log Packaging Rules

Logs are packaged on an hourly basis by default. If there are no requests for accessing your business within an hour, no log packages will be generated for the time interval.
Since EdgeOne nodes are distributed globally, the storage time of offline logs (the time in log package filenames) is set to UTC +00:00 by default in order to synchronize all time zones.
Offline logs are collected from various EdgeOne nodes so that they are different in latency. Generally, logs can be queried and downloaded after a delay of around 3 hours. The log packages will increase continuously and typically stabilize after around 24 hours.

Log Retention Period

The default retention period of offline logs is 31 days. For sites with Standard and Enterprise plans, the retention period of offline logs can be adjusted to 183 days to meet relevant compliance requirements. For details, see Plan Support Differences.

Directions

1. Log in to the EdgeOne console and click Site List in the left sidebar. Then click the site of your concern in the site list.
2. On the site details page, click Log Service > Offline Logs.
3. On the offline logs page, click Settings

on the right side of the filter field.

4. In the pop-up window, modify the retention period of offline logs and click Save . After you modify the log retention period, the logs stored before the modification will be eliminated according to the original retention period, and the newly stored logs will be eliminated according to the modified retention period.


Example: Querying Offline Logs for a Specified Domain Name within a Specified Time Period

Sample Scenario

After you add an acceleration domain name and add www.example.com to the EdgeOne service, you shall download all site acceleration logs for www.example.com from June 23, 2024 to June 25, 2024 to perform data analysis. You can refer to the following directions.

Directions

1. Log in to the EdgeOne console and click Site List in the left sidebar. Then click the site of your concern in the site list, to enter the site details page.
2. On the site details page, click Log Service > Offline Logs.
3. On the offline logs page, select the dates from June 23, 2024 to June 25, 2024 to filter by time range. On the right side, select Site Acceleration Logs as the log type and www.example.com as the domain name. The page will automatically display the query results of logs meeting the conditions after filtering.

4. In the log list obtained through query, you can download log packages as needed using the following 3 methods:
Click Download in the Operation column, to download the log package for the corresponding domain name/L4 proxy instance and the corresponding time period.
Click Get Download URLs, to copy the download link for the corresponding log package.
Select the required log packages, and click Batch Get Download URLs to copy the download links for all required log packages in batch.

Related APIs