All Products
Search
Document Center

Object Storage Service:Metrics

Last Updated:Mar 20, 2026

Object Storage Service (OSS) provides two tiers of monitoring metrics: user-level metrics that cover all buckets under an Alibaba Cloud account, and bucket-level metrics that track the performance and usage of individual buckets.

OSS computes and reports three types of measurements:

Metric typeReporting intervalDescription
Aggregate metrics (sums, averages, maximums)One minuteNear-real-time request and traffic statistics
Billable usage metricsOne hourResource consumption used for billing calculations
Monthly statisticsCumulativeTotals from 00:00:00 on the first day of the current month to the time you view the data
CloudMonitor's default dashboard displays monitoring data for Elastic Compute Service (ECS) instances. To view OSS metrics, click Add View in the CloudMonitor console to add them to the dashboard. For details, see Manage the monitoring charts of a custom dashboard.

User-level metrics

User-level metrics reflect aggregate usage across all OSS buckets owned by an Alibaba Cloud account. They cover three areas: monthly statistics, monitoring service overview, and request status details.

Monthly statistics

These metrics track cumulative resource consumption from 00:00:00 on the first day of the current month to the time you view the data.

Metric nameUnitDescription
Storage sizeByteTotal storage used by all buckets under the account during the current month.
Internet outbound trafficByteTotal Internet outbound traffic generated by the account during the current month.
Number of PUT requestsCountTotal PUT requests made by the account during the current month.
Number of GET requestsCountTotal GET requests made by the account during the current month.

Monitoring service overview

These metrics describe the overall health and traffic of the OSS service for the account.

Metric nameUnitDescription
Availability by User%System availability of OSS, calculated as: 1 - Server error requests with the returned HTTP status code 5xx/All requests.
Valid Request Proportion by User%Percentage of valid requests (HTTP 2xx and 3xx) out of all requests.
Number of Total Requests by UserCountTotal requests received and processed by the OSS server.
Number of Valid Requests by UserCountTotal requests with HTTP status codes 2xx and 3xx.
Internet Outbound Traffic by UserByteOutbound traffic sent over the Internet.
Internet Inbound Traffic by UserByteInbound traffic received over the Internet.
Intranet Outbound Traffic by UserByteOutbound traffic sent over the internal network.
Intranet Inbound Traffic by UserByteInbound traffic received over the internal network.
CDN Outbound Traffic by UserByteOutbound traffic sent over Content Delivery Network (CDN) after CDN is activated. This traffic represents back-to-origin traffic.
CDN Inbound Traffic by UserByteInbound traffic received over CDN after CDN is activated.
Cross-region Sync Outbound Traffic by UserByteOutbound traffic generated during data replication after cross-region replication (CRR) is enabled.
Cross-region Sync Inbound Traffic by UserByteInbound traffic generated during data replication after CRR is enabled.

Request status details

These metrics break down requests by HTTP status code and OSS error code.

Metric nameUnitDescription
Number of Server Error Requests by UserCountTotal requests with HTTP status code 5xx.
Server Error Request Proportion by User%Percentage of 5xx error requests out of all requests.
Number of Network Error Requests by UserCountTotal requests with HTTP status code 499.
Network Error Request Proportion by User%Percentage of 499 error requests out of all requests.
Number of Authorization Error Requests by UserCountTotal requests with HTTP status code 403.
Authorization Error Request Proportion by User%Percentage of 403 error requests out of all requests.
Number of Resource Not Found Error Requests by UserCountTotal requests with HTTP status code 404.
Resource Not Found Error Request Proportion by User%Percentage of 404 error requests out of all requests.
Number of Client Timeout Error Requests by UserCountTotal requests with HTTP status code 408 or OSS error code RequestTimeout.
Client Timeout Error Request Proportion by User%Percentage of client timeout error requests out of all requests.
Number of Client Other Error Requests by UserCountTotal 4xx requests other than the preceding client-side error requests (excluding HTTP status code 408 and OSS error code RequestTimeout).
Client Other Error Request Proportion by User%Percentage of other 4xx error requests out of all requests.
Number of Successful Requests by UserCountTotal requests with HTTP status code 2xx.
Successful Request Proportion by User%Percentage of 2xx requests out of all requests.
Number of Redirected Requests by UserCountTotal requests with HTTP status code 3xx.
Redirected Request Proportion by User%Percentage of 3xx requests out of all requests.

Bucket-level metrics

Bucket-level metrics cover everything in user-level metrics, plus measurement and performance metrics specific to each bucket.

Important

Bucket-level and user-level metrics for the same dimension measure different things. For example, the user-level storage size metric is the cumulative storage used by all buckets since the start of the current month. The bucket-level storage size metric is the storage occupied by a single bucket during a specific hour.

Measurement reference

These metrics are reported at one-hour intervals and track resource consumption per bucket.

Metric nameUnitDescription
Storage SizeByteStorage occupied by the bucket each hour.
Internet Outbound TrafficByteTotal Internet outbound traffic from the bucket each hour.
Number of PUT RequestsCountTotal PUT requests to the bucket each hour.
Number of GET RequestsCountTotal GET requests to the bucket each hour.

Latency

Latency metrics track system performance at one-minute intervals. They cover only successful requests with HTTP status code 2xx.

OSS reports two latency dimensions for each operation:

  • End-to-end (E2E) latency — the total time from when OSS receives a request to when it receives acknowledgment of the response. E2E latency includes network time.

  • Server latency — the time OSS takes to process a request. Server latency excludes network time.

Each dimension reports both average and maximum values. The following request types are covered: GetObject, HeadObject, PutObject, PostObject, AppendObject, UploadPart, and UploadPartCopy.

Metric nameUnitDescription
GetObject Request Average E2E LatencyMillisecondAverage end-to-end latency of successful GetObject requests.
GetObject Request Average Server LatencyMillisecondAverage server latency of successful GetObject requests.
GetObject Request Maximum E2E LatencyMillisecondMaximum end-to-end latency of successful GetObject requests.
GetObject Request Maximum Server LatencyMillisecondMaximum server latency of successful GetObject requests.
HeadObject Request Average E2E LatencyMillisecondAverage end-to-end latency of successful HeadObject requests.
HeadObject Request Average Server LatencyMillisecondAverage server latency of successful HeadObject requests.
HeadObject Request Maximum E2E LatencyMillisecondMaximum end-to-end latency of successful HeadObject requests.
HeadObject Request Maximum Server LatencyMillisecondMaximum server latency of successful HeadObject requests.
PutObject Request Average E2E LatencyMillisecondAverage end-to-end latency of successful PutObject requests.
PutObject Request Average Server LatencyMillisecondAverage server latency of successful PutObject requests.
PutObject Request Maximum E2E LatencyMillisecondMaximum end-to-end latency of successful PutObject requests.
PutObject Request Maximum Server LatencyMillisecondMaximum server latency of successful PutObject requests.
PostObject Request Average E2E LatencyMillisecondAverage end-to-end latency of successful PostObject requests.
PostObject Request Average Server LatencyMillisecondAverage server latency of successful PostObject requests.
PostObject Request Maximum E2E LatencyMillisecondMaximum end-to-end latency of successful PostObject requests.
PostObject Request Maximum Server LatencyMillisecondMaximum server latency of successful PostObject requests.
AppendObject Request Average E2E LatencyMillisecondAverage end-to-end latency of successful AppendObject requests.
AppendObject Request Average Server LatencyMillisecondAverage server latency of successful AppendObject requests.
AppendObject Request Maximum E2E LatencyMillisecondMaximum end-to-end latency of successful AppendObject requests.
AppendObject Request Maximum Server LatencyMillisecondMaximum server latency of successful AppendObject requests.
UploadPart Request Average E2E LatencyMillisecondAverage end-to-end latency of successful UploadPart requests.
UploadPart Request Average Server LatencyMillisecondAverage server latency of successful UploadPart requests.
UploadPart Request Maximum E2E LatencyMillisecondMaximum end-to-end latency of successful UploadPart requests.
UploadPart Request Maximum Server LatencyMillisecondMaximum server latency of successful UploadPart requests.
UploadPartCopy Request Average E2E LatencyMillisecondAverage end-to-end latency of successful UploadPartCopy requests.
UploadPartCopy Request Average Server LatencyMillisecondAverage server latency of successful UploadPartCopy requests.
UploadPartCopy Request Maximum E2E LatencyMillisecondMaximum end-to-end latency of successful UploadPartCopy requests.
UploadPartCopy Request Maximum Server LatencyMillisecondMaximum server latency of successful UploadPartCopy requests.

Successful request category

These metrics count successful requests by operation type, reflecting the system's request processing capacity.

Metric nameUnitDescription
Successful GetObject RequestCountNumber of successful GetObject requests.
Successful HeadObject RequestCountNumber of successful HeadObject requests.
Successful PutObject RequestCountNumber of successful PutObject requests.
Successful PostObject RequestCountNumber of successful PostObject requests.
Successful AppendObject RequestCountNumber of successful AppendObject requests.
Successful UploadPart RequestCountNumber of successful UploadPart requests.
Successful UploadPartCopy RequestCountNumber of successful UploadPartCopy requests.
Successful DeleteObject RequestCountNumber of successful DeleteObject requests.
Successful DeleteObjects RequestCountNumber of successful DeleteObjects requests.

Mirroring-based back-to-origin

These metrics track traffic and performance for mirroring-based back-to-origin requests. Metrics without "by Status" in the name cover requests with returned values 200 and 206. Metrics with "by Status" in the name cover requests with a specific returned value.

Metric nameUnitDescription
Mirror Inbound TrafficByteTotal inbound traffic from requests with returned values 200 and 206 for a specific origin.
Mirror Inbound Traffic by StatusByteInbound traffic from requests with a specific returned value for a specific origin.
Mirror Request Average Transfer SpeedByte/sAverage transfer speed of requests with returned values 200 and 206 for a specific origin.
Mirror Request Average Transfer Speed by StatusByte/sAverage transfer speed of requests with a specific returned value for a specific origin.
Mirror Request CountCountTotal requests with returned values 200 and 206 for a specific origin.
Mirror Request Count by StatusCountTotal requests with a specific returned value for a specific origin.
Mirror Request Average LatencyMillisecondAverage latency of requests with returned values 200 and 206 for a specific origin.
Mirror Request Average Latency by StatusMillisecondAverage latency of requests with a specific returned value for a specific origin.
Mirror Request Proportion by Status%Proportion of requests with a specific status code (2xx, 3xx, 4xx, or 5xx) for a specific origin out of all requests.
Mirror Request with a Specific Status Code CountCountNumber of requests with a specific status code (2xx, 3xx, 4xx, or 5xx) for a specific origin.