For analysis or auditing purposes, users can enable the log management function. By accessing the log, the bucket owner can deeply analyze the nature, type or trend of user request to access the bucket. When the log function is enabled for a bucket, ZOS will automatically log the access request of this bucket, and generate a log file to write into the bucket specified by the user.

Logs stored in ZOS will also occupy the storage space in ZOS of the tenant, meaning that additional storage costs will be incurred. By default, ZOS will not enable the log management function for users.

Log file format:

The format of a log file consists of: The following names, from left to right, are separated by spaces.

Name	Example	Meaning
owner_id	testuser	Source bucket ownerid
bucket	sbucket	Source bucket name
time	[23/Aug/2020:10:00:42+0800]	Access time
remote_addr	192.168.56.123	IP address where the request is originated
user	testuser	Executive user
request_id	tx00000000000000000001c-005f41cdca-a222f-default	ID used to uniquely identify the request
operation	REST.GET.ACL	Request type
oname	obj_name	Object name
uri	GET/sbucket?aclHTTP/1.1	URI requested by the user
http_status	200	HTTP status code returned
error_code	-	Error code returned
bytes_sent	441	User download traffic
obj_size	0	Object size
total_time	1	Time taken to process this request (ms)
referrer	-	Requested httpreferer
user_agent	Boto3/1.4.6Python/2.7.5Linux/3.10.0-1062.el7.x86_64Botocore/1.8.35	User-agent header of http
oversion_id	-	Version ID

A "-" may appear in any field in a log to indicate unknown data or that the field is invalid for the current request.

Zettabyte Object Storage

Brief Introduction to Log Management