tencent cloud

Tencent Cloud EdgeOne

Release Notes and Announcements
Release Notes
Security Announcement
Announcements
Product Introduction
Overview
Strengths
Use Cases
Comparison Between EdgeOne and CDN Products
Use Limits
Purchase Guide
Description of Trial Plan Experience Benefits
Free Plan Guide
Billing Overview
Billing Items
Subscriptions
Renewals
Instructions for overdue and refunds
Comparison of EdgeOne Plans
About "clean traffic" billing instructions
DDoS Protection Capacity Description
Getting Started
Choose business scenario
Quick access to website security acceleration
Quick deploying a website with Pages
Domain Service&Origin Configuration
Domain Service
HTTPS Certificate
Origin Configuration
Site Acceleration
Overview
Access Control
Smart Acceleration
Cache Configuration
File Optimization
Network Optimization
URL Rewrite
Modifying Header
Modify the response content
Rule Engine
Image&Video Processing
Speed limit for single connection download
DDoS & Web Protection
Overview
DDoS Protection
Web Protection
Bot Management
API Discovery(Beta)
Edge Functions
Overview
Getting Started
Operation Guide
Runtime APIs
Sample Functions
Best Practices
Pages
L4 Proxy
Overview
Creating an L4 Proxy Instance
Modifying an L4 Proxy Instance
Disabling or Deleting an L4 Proxy Instance
Batch Configuring Forwarding Rules
Obtaining Real Client IPs
Data Analysis&Log Service
Log Service
Data Analysis
Alarm Service
Site and Billing Management
Billing Management
Site Management
Version Management
General Policy
General Reference
Configuration Syntax
Request and Response Actions
Country/region and Corresponding Codes
Terraform
Overview
Installing and Configuring Terraform
Practical Tutorial
EdgeOne Skill User Guide
Automatic Warm-up/Cache Purge
Resource Abuse/hotlinking Protection Practical
HTTPS Related Practices
Acceleration Optimization
Scheduling Traffic
Data Analysis and Alerting
Log Platform Integration Practices
Configuring Origin Servers for Cloud Object Storage (Such As COS)
CORS Response Configuration
API Documentation
History
Introduction
API Category
Making API Requests
Site APIs
Acceleration Domain Management APIs
Site Acceleration Configuration APIs
Edge Function APIs
Alias Domain APIs
Security Configuration APIs
Layer 4 Application Proxy APIs
Content Management APIs
Data Analysis APIs
Log Service APIs
Billing APIs
Certificate APIs
Origin Protection APIs
Load Balancing APIs
Diagnostic Tool APIs
Custom Response Page APIs
API Security APIs
DNS Record APIs
Content Identifier APIs
Legacy APIs
Ownership APIs
Image and Video Processing APIs
Multi-Channel Security Gateway APIs
Version Management APIs
Data Types
Error Codes
FAQs
Product Features FAQs
DNS Record FAQs
Domain Configuration FAQs
Site Acceleration FAQs
Data and Log FAQs
Security Protection-related Queries
Origin Configuration FAQs
Troubleshooting
Reference for Abnormal Status Codes
Troubleshooting Guide for EdgeOne 4XX/5XX Status Codes
520/524 Status Code Troubleshooting Guide
521/522 Status Code Troubleshooting Guide
Tool Guide
Agreements
Service Level Agreement
Origin Protection Enablement Conditions of Use
TEO Policy
Privacy Policy
Data Processing And Security Agreement
Contact Us
Glossary

Overview

PDF
Focus Mode
Font Size
Last updated: 2026-03-19 14:35:07
The L4/7 acceleration, web protection, edge function,and other feature modules of EdgeOne global availability zone nodes support recording detailed logs when processing requests for your services. The CLS module collects and aggregates logs from various feature modules, and then provides the logs to users. You can use the log details for troubleshooting, checking the impact of configuration updates, generating monitoring metrics, etc.

Supported Features

Log Analytics (Beta): Deliver Layer 7 Access Logs (including Web protection interception logs) to the EdgeOne console "Log Analytics" with low latency, supporting custom sampling rates and default 31-day log storage. Support through the console to search, analyze, and download logs within these 31 days, helping you quickly gain traffic trend insights, identify security risks, and optimize site performance.
Note:
Log Analytics (Beta) is in beta. If necessary, please contact us.
Currently, the Beta version only supports Layer 7 access logs (including Web protection interception logs). Other types of logs will be supported subsequently.
Real-time Log Push: Ships the access request logs to your specified destination with low latency, and supports configuration through the console or API. The latency from initiating a request to receiving the logs by the destination is within 5 minutes. It is suitable for scenarios requiring high timeliness such as real-time troubleshooting and monitoring. The recording scopes for various types of request logs are described as follows.
Site Acceleration Logs: Records the domain access logs. By default, only the logs of requests after protection are recorded. Logs of the requests blocked by Anti-DDoS are not recorded.
Note:
The feature of Real-time Logs - Site Acceleration Logs to record full L7 request logs (including L7 protection block logs) is in beta testing. If needed, please contact us.
L4 Proxy Logs: Records the access logs of L4 proxy instances. Only the logs of accesses after protection are recorded. Logs of the accesses blocked by Anti-DDoS are not recorded.
Edge Function Running Logs: Records logs of the edge function execution situation.
Rate Limiting and CC Attack Protection Logs: Only records the request logs that match the security rules of the L7 Protection - Rate Limiting and CC Attack Protection module, no matter whether the requests are blocked or not.
Managed Rule Logs: Only records the request logs that match the security rules of the L7 Protection - Managed Rules module, no matter whether the requests are blocked or not.
Custom Rule Logs: Only records the request logs that match the security rules of the L7 Protection - Custom Rules module, no matter whether the requests are blocked or not.
Bot Management Logs: Only records the request logs that match the security rules of the L7 Protection - Bot Management module, no matter whether the requests are blocked or not.
Offline Logs: By default, the access logs are retained for 30 days. You can obtain the download URL for the log package via the console or API. Usually, the download URL for the log package is available 3 hours after a request is initiated, and the integrity of the logs within the log package will be guaranteed after 24 hours. It is suitable for scenarios not requiring high timeliness, such as long-term log retention and periodic reconciliation.
Site Acceleration Logs: Records the domain access logs. Only the logs of requests after protection are recorded. Logs of the requests blocked by Anti-DDoS are not recorded.
L4 Proxy Logs: Records the access logs of L4 proxy instances. Only the logs of accesses after protection are recorded. Logs of the accesses blocked by Anti-DDoS are not recorded.
Note:
For real-time and offline log field descriptions, please refer to Field description.

Package Support Differences

Sub-feature
Individual Edition
Basic Edition
Standard Edition
Enterprise Edition
Log Analysis(Beta)
Feature in beta test, if needed
Real-time Log Push
2 Task/Log Types
2 Task/Log Types
3 Task/Log Types
5 Task/Log Types
Offline Logs
Supported. The log retention duration is 30 days.
Supported. The default log retention duration is 31 days, and the maximum log retention duration is 183 days.

Billing Description

Log Analysis

Log Analysis (Beta) is free to use during the beta test period. After the official launch, it will convert to Pay-As-You-Go billing.

Real-time Log Push

After accessing EdgeOne, you will obtain the real-time log push feature by default, without any additional charges.
It's important to note that after you configure real-time log push tasks, the destination of log shipping may also incur charges. For example, after configuring log push to Tencent Cloud CLS, traffic and storage charges may be generated for the Tencent Cloud CLS product. For details, refer to CLS Billing Overview.

Offline Logs

After integration with EdgeOne, the offline log feature is disabled by default and can be used for free once activated.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback