Log Collection

Why Are There Lost or Duplicate Logs?

• Lost logs

  Cause 1: The log storage duration exceeds the LTS log storage duration.

  Description: CCI 2.0 collects application logs and reports them to LTS. Logs reported to LTS will be deleted in the early morning of the next day after the log storage duration expires. You can transfer logs to OBS buckets for long-term storage.

  Cause 2: The log file exists for fewer than 5 seconds.

  Description: CCI detects log files at an interval of 5 seconds. If the duration from the time a log file is created to the time it is deleted or renamed is less than 5 seconds, it may not be collected.

• Duplicate logs

  Cause 1: The log file is dumped, and the dumped file is still matched.

  Description: If the file name of the configured log path contains a wildcard character, for example, /tmp/*.log, after the /tmp/test.log file is dumped to /tmp/test.001.log, it is still matched by the wildcard rule and is collected again as a new file.

Why Is No Data Displayed During Log Collection?

• Cause 1: logconf.k8s.io/fluent-bit-log-type: lts is not configured when TLS is used to collect logs.
• Cause 2: The log stream ID is incorrect.

  Refer to the following documents for solutions:

  • Using CCI through the CCI console: Log Collection
  • Using CCI through CCE: Collecting Logs Using LTS

Why Did the Parameter Verification Fail for Log Collection?

The log stream ID is incorrect. To solve the problem, refer to the following documents:

• Using CCI through the CCI console: Log Collection
• Using CCI through CCE: Collecting Logs Using LTS