CDN can collect and publish access logs in real time, enabling fast retrieval and analysis of log data. You can quickly access comprehensive, stable, and reliable one-stop logging services such as log collection, log storage, and log search in the CDN console.
- Real-time Logs is now officially launched. You can log in to the console with a root account and activate it. Note that you need to complete authorization and activate the Cloud Log Service before first use.
- Real-time Logs currently does not support log shipping in regions outside the Chinese mainland.
- Real-time Logs can only be activated by a root account.
- CDN and ECDN domain names cannot be added to the same log topic.
This feature can be used to view and analyze user access in real time.
A logset is a project management unit in the log service. It is used to distinguish between logs of different projects and corresponds to an item or application. The CDN logset has the following basic attributes:
A log topic is the basic management unit in the log service. One logset can contain multiple log topics, and one log topic corresponds to one type of application or service. We recommend you collect similar logs on different machines into the same log topic. For example, if a business project has three types of logs: operation log, application log, and access log, you can create a log topic for each type of log.
The log service system manages different log data based on different log topics. Each log topic can be configured with different data sources, index rules, and shipping rules. Therefore, a log topic is the basic unit for configuring and managing log data in the log service. You need to configure corresponding rules first after creating a log topic before you can perform log collection, search, analysis, and shipping.
Log topic features include:
Log in to the CDN console, click Log Service on the left sidebar, and open the Real-time Log tab to create real-time log shipping.
Click Create to create a log topic.
Up to 10 log topics can be created under one logset.
Enter the name of the new log topic and select the domain names to be bound to this topic.
- The name of the new log topic cannot be the same as the name of any existing log topic.
- A domain name can be bound to only one log topic.
- After the configuration information is saved, it takes about 15 minutes for the configuration to take effect.
After successfully configuring a log topic, you can perform log topic management. Specifically, you can stop/start shipping logs to the log topic, search for logs in log topic, manage the log topic, and delete the log topic.
You can manually stop/start shipping logs to a log topic.
- After a log topic is stopped, all logs of the domain names bound to the log topic will no longer be shipped to it. Logs that have already been shipped to it will be retained. This operation will take effect in about 5–15 minutes.
- After a log topic is started, all logs of the domain names bound to the log topic will be shipped to it. This operation will take effect in about 5–15 minutes.
You can search for logs by log topic. Select a desired log topic and click Search to access the log search page.
You can manage a created log topic and update the list of domain names bound to it.
The new configuration will take effect in 5 to 15 minutes.
You can delete log topics manually.
After a log topic is deleted, all logs of the domain names bound to the log topic will no longer be shipped to it, and the logs that have already been shipped to the log topic will be completely cleared. This operation will take effect in about 5–15 minutes.
|Log Field||Raw Log Type||Log Service Type||Description|
|app_id||Integer||long||Tencent Cloud account
|hit||String||text||Cache hit/miss. Both hits on CDN edge servers and parent nodes are marked as hit|
|http_code||Integer||long||HTTP status code|
|param||String||text||Parameter carried in URL|
|proto||String||text||HTTP protocol identifier|
|referer||String||text||Referer information, i.e., HTTP source address|
|request_range||String||text||Range parameter, i.e., request range|
|request_time||Integer||long||Response time (in milliseconds), which refers to the time it takes for a node to respond to a client with all return packets after receiving a request|
|rsp_size||Integer||long||Number of returned bytes|
|time||Integer||long||Request timestamp in UNIX format (in seconds)|
|uuid||String||text||Unique request ID|
|version||Integer||long||CDN real-time log version|