The log management feature allows you to record the detailed access information of a specified source bucket and save the information as log files to a specified bucket for better bucket management.
The current use limits on the log management feature are shown below:
- Limit on shipping frequency: A log is generated every 5 minutes.
- Limit on the size of log files to be shipped: The log file to be shipped each time can be up to 256 MB. If a file exceeds this limit, its surplus part will be shipped as a new file.
- Limit on the format of logs to be shipped: There is one record per line. Each record contains multiple fields, which are separated by a space.
- Limit on the fields to be shipped: For more information on the fields to be shipped, see the description in "Logging Overview".
- Limit on invalid fields: If a field in a log contains the "-" character, the field is an invalid record or the default record.
Content Recorded in a Log
The requests you initiate to upload, download, and delete an object, as well as to create and delete a bucket, and to modify the bucket configuration.
Content Not Recorded in a Log
- Offline origin-pull requests: After you configure origin-pull, if there are no objects in COS, the data will be downloaded from the origin server you specify. This download operation is an offline origin-pull request and will not be recorded in the log.
- Operations of redirects within a static website: After you configure redirection in the static website feature, you might be redirected to another page when accessing index.html. These redirection operations will not be recorded in the log.
- Operations of lifecycle transitions and deletions: After you configure the lifecycle feature to transition or delete objects after expiration, these transition and deletion operations will be implemented by the COS backend and will not be recorded in the log.
- Operations of listing objects and uploading inventory reports: The inventory feature periodically lists all or specified objects in your buckets for you and ships the generated inventory report to your buckets. The operations of listing objects and shipping inventory reports will not be recorded in the log.
- Operations of cross-region object replication: Cross-region replication requires getting an object from the source bucket and uploading the object to the destination bucket. These operations are implemented by the COS backend and will not be recorded in the log.
- Operations of object downloads in the COS Select feature: The COS Select feature helps you search for an object, but the search can only be performed after the data is obtained from a storage device. The operations of object downloads are implemented by the COS backend and will not be recorded in the log.