tencent cloud

1. Configure log collection as instructed in Using Environment Variables to Configure Log Collection
2. If you want to use keys for authorization, you can create a Secret in Opaque type and create two keys (SecretId and SecretKey). The values of SecretId and SecretKey can be obtained in API Key.
3. You can find the created Secret after enabling log collection and associate SecretId with SecretKey
4. Get the raw logs in the console, switch to the table view, and format the JSON strings

This method has a problem: the log collection feature of TKE Serverless works by sending the collected logs as JSON strings to the specified consumer, but the timestamps of the collected JSON strings are at the second level

In this case, logs are displayed in the console at the second level, and the logs displayed on the search and analysis page can be sorted only by second but cannot be output sequentially at a finer time granularity. However, sometimes a large number of logs are output in a short while, for which a millisecond granularity is often required. Therefore, we recommend the CRD-based configuration method.

1. Configure log collection as instructed in Configuring Log Collection via the Console.
2. After enabling log collection, create a log rule as shown below:
   
   On the search and analysis page, you can see that the time granularity is millisecond, and logs can be output sequentially by millisecond.
   >?CRD-Based log collection configuration also supports separating raw logs with regular expressions, which is more flexible but more complicated than configuration through environment variables.

Problems that may occur in log collection configuration

• If you select CRD-based log collection configuration, please use a browser with the Chrome kernel, such as the latest version of Edge and Chrome instead of early versions of Edge. As the frontend may not support legacy kernels, problems such as improper display of sample logs and failure to select automatically generated regular expressions may occur.
• After you use CRDs to configure log collection, you do not need to perform other operations when creating a Pod, and the output logs will be collected automatically. If no logs are collected, check whether the server group is full. After there is any available server in the server group, you can restart the Pod of cls-provisioner.