Help Center/ Object Storage Service/ User Guide/ Monitoring and Logging/ Using Logging to Record OBS Access Requests/ Log Management Overview
Updated on 2026-11-02 GMT+08:00
View PDF
Share

Log Management Overview

Scenarios

When storing and managing large volumes of data in OBS, you can use log management to audit operations, troubleshoot issues, and analyze data more efficiently. Once enabled, OBS automatically records detailed bucket access requests, including requester IP addresses and operation types, and periodically stores the log files. You can use Log Tank Service (LTS) to search and analyze these logs, improving operational efficiency.

Important Notes

By default, OBS does not collect bucket access logs. You must enable log storage or log analysis manually.

How It Works

As shown in the following figure, OBS provides two features: log storage and log analysis.

  • Log storage: Records bucket access requests and stores the generated log files in a specified bucket.
  • Log analysis: Records bucket access requests and uses LTS log search and analysis capabilities to enable real-time log analysis.

How Log Storage Works

Figure 1 Log storage

  1. OBS records access requests to bucket A and generates log files for the bucket.
  2. OBS stores the log files in a specified OBS bucket.
  3. You can process the log files as needed, such as deleting them or transitioning them to a lower-cost storage class.

How Log Analysis Works

  1. OBS records access requests to a bucket and generates log files for the bucket.
  2. LTS dynamically collects OBS logs.
  3. You can initiate log search and analysis requests through the console.
  4. LTS analyzes the log files collected in 2 and returns the search and analysis results to OBS Console.

Feature Comparison

Dimension

Log Storage

Log Analysis

Use case

Log storage

Real-time log analysis

Logged fields

See Log Storage Fields.

See Log Analysis Fields.

Latency

Longer. Log files are available in the log storage bucket after about 15 minutes. Subsequent log files are generated and stored every hour. Logs for a given period may not include every request made during that period. Some requests may be written to the log files of the previous or next period.

Shorter. There is a delay of about 3 minutes. Request logs are typically available on the Log Analysis page of the console about 3 minutes after the requests are sent.

Billing

Log files are stored in an OBS bucket and incur storage charges. You can use lifecycle management to periodically transition log files to a different storage class or delete them based on your needs.
  • LTS dynamically collects and stores log data. You are billed for log storage. You can configure the storage period as needed. For details, see Log Analysis Procedure.
  • Uploading log data to LTS incurs log read/write traffic charges.
  • Log search and analysis incur charges for index traffic - standard log streams.

For details, see LTS Billing.
Parent Topic: Using Logging to Record OBS Access Requests