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
이 페이지는 현재 영어로만 제공되며 한국어 버전은 곧 제공될 예정입니다. 기다려 주셔서 감사드립니다.

Push to Tencent Cloud CLS

EdgeOne Real-Time Log Push supports pushing logs to Tencent Cloud Log Service (CLS). You can configure it through the console or API. For more information about CLS, refer to CLS Product Documentation.

Prerequisites

1. Log in to the Tencent Cloud CLS console and activate CLS.
2. If you wish to use a sub-account for CLS-related operations, refer to CLS Permission Management Guide, to complete sub-account authorization and ensure that the sub-account has related read and write permissions for CLS log sets and log topics.
Note:
You must authorize EdgeOne to access your log sets and log topics through the service role TEO_QCSLinkedRoleInRealTimeLogCLS. EdgeOne will use the service role to query log sets and log topics, modify index configurations, and push logs.

Directions

1. Log in to the EdgeOne console and click Site List in the left sidebar. Then click on the site to be configured in the site list, to enter the site details page.
2. On the site details page, click Log Service > Real-time Logs.
3. On the real-time logs page, click Create Push Task.
4. On the log source selection page, enter a task name, select a log type, service area, and domain name/L4 proxy instance requiring log push, and click Next.
5. On the push content definition page:
(Required) Check the log fields to be pushed from the predefined field list.
(Optional) Add a custom log field, which supports extracting specified field names from the request headers, response headers, and Cookie headers.
(Optional) Configure the log push filter conditions. Full logs are pushed by default.
(Optional) In advanced configuration, set the sampling ratio. By default, sampling is not enabled and 100% of logs are pushed to the destination.
(Optional) In advanced configuration, set the log output format. The default format is JSON Lines.
Note:
For pushing logs to CLS, only the JSON format can be selected. Prefixes, suffixes, and separators are not effective.
6. On the destination selection page, select CLS and click Next.
7. On the destination information page, select the region, log set, and log topic for the destination log set.
Note:
Due to the write operation permission restrictions of Serverless Cloud Function (SCF) on the CLS log topic, during configuration of the EdgeOne real-time log shipping destination, do not select the SCF Default Log Topic to avoid shipping failure or inability to search logs.
8. Click Push, confirm the related cost tips in the pop-up window, and click Confirm Creation.
9. In the pop-up window, select the index configuration method. It is recommended to click Quick Index Configuration. EdgeOne will create a key-value index for the previously selected log topic. You can also configure the index yourself in the CLS Console. Note that if Key-Value Index is not enabled, you will fail to search logs.
Note:
When the log volume is too large, and the log topic auto-split feature of CLS is disabled or the partition value has reached its limit, CLS will restrict the log push request frequency, which may result in log data loss. To avoid such issues, refer to CLS Log Topic for configuration.