The access logs of CLB collect and record the details of each client request, such as the request time, request path, client IP and port, return code, and response time, which can help you better understand client requests, troubleshoot issues, and analyze user behaviors.
- The feature of storing access logs in COS will stop accepting new enablement requests after 00:00:00, May 15, 2020 (00:00:00, April 26, 2020 for the Guangzhou region) and will be officially disused after 00:00:00, June 30, 2020. For more information, please see Announcement on the Deactivation of the Feature of Storing CLB Access Logs in COS. Please use the upgraded feature of storing access logs in CLS.
- Access logs can be configured only for layer-7 CLB but not layer-4 CLB.
- Currently, access logs can only be configured in certain regions. For more information, please see below.
There are two methods for storing the access logs of CLB:
|Item||Storing Access Logs in CLS||Storing Access Logs in COS|
|Time granularity for getting logs||Minute||Hour|
|Online search||Supported||Not supported. You must download an access log for data search|
|Search syntax||Full-text search, key-value search, fuzzy keyword search, etc. For more information, please see Search Rules||Typically full-text search|
|Supported regions||It is supported in Guangzhou, Shanghai, Chengdu, Hong Kong (China), Nanjing, Beijing, Chongqing, Singapore, Mumbai, Silicon Valley, Tokyo, and Frankfurt.||Guangzhou, Shanghai, Beijing, Hong Kong (China)|
|Supported types||Public network/private network CLB||Public network CLB|
|Upstream and downstream links||CLS logs can be stored in COS, and consumed using CKafka||-|
|Log Retention||Tencent Cloud stores no access log by default. You need to store the access log in CLS as needed.||Tencent Cloud will retain the logs for three days by default in the regions that support storing access logs in COS.|