OBS Monitoring Metrics
Functions
This section defines the namespace, list, and dimensions of monitoring metrics reported by OBS to Cloud Eye. You can use the management console or API provided by Cloud Eye to search for monitoring metrics and alarms generated by OBS.
Namespace
SYS.OBS
Monitoring Metrics (Open)
The metrics in the following table apply to the regions except CN North-Beijing1, CN North-Beijing4, CN East-Shanghai1, CN East-Shanghai2, CN Southwest-Guiyang1, CN South-Guangzhou, CN-Hong Kong, AP-Bangkok, AP-Singapore, and AF-Johannesburg. For monitoring metrics about these listed regions, see Monitoring Metrics (OBT).
|
Metric ID |
Metric |
Description |
Value Range |
Measurement Object & Dimension |
Monitoring Period (Original Metric) |
|---|---|---|---|---|---|
|
download_bytes |
Bytes Downloaded |
Specifies the response bytes of all download requests made to all buckets in a region, including bytes in HTTP entity bodies. Unit: byte |
≥ 0 bytes |
Bucket |
5 min |
|
upload_bytes |
Bytes Uploaded |
Specifies the bytes of all upload requests made to all buckets in a region, including bytes in HTTP entity bodies. Unit: byte |
≥ 0 bytes |
Bucket |
5 min |
|
get_request_count |
GET Requests |
Specifies the number of GET, HEAD, or OPTIONS requests made to all buckets and objects in the buckets of a region. Unit: count |
≥ 0 counts |
Bucket |
5 min |
|
put_request_count |
PUT Requests |
Specifies the number of PUT, POST, and DELETE requests made to all buckets and objects in the buckets of a region. Unit: count |
≥ 0 counts |
Bucket |
5 min |
|
first_byte_latency |
First Byte Download Delay |
Specifies the average time from receiving a GET, HEAD, or OPTIONS request to the time that the system starts to respond in a measurement period. Unit: millisecond |
≥ 0 ms |
Bucket |
5 min |
|
request_count_4xx |
4xx Errors |
Specifies the times that the server responds to requests whose error codes are 4xx. Unit: count |
≥ 0 counts |
Bucket |
5 min |
|
request_count_5xx |
5xx Errors |
Specifies the times that the server responds to requests whose error codes are 5xx. Unit: count |
≥ 0 counts |
Bucket |
5 min |
Monitoring Metrics (OBT)
The following monitoring metrics are available only in the CN North-Beijing1, CN North-Beijing4, CN East-Shanghai1, CN East-Shanghai2, CN Southwest-Guiyang1, CN South-Guangzhou, CN-Hong Kong, AP-Bangkok, AP-Singapore, and AF-Johannesburg regions.
|
Metric ID |
Metric |
Description |
Value Range |
Measurement Object & Dimension |
Monitoring Period (Original Metric) |
|---|---|---|---|---|---|
|
get_request_count |
GET Requests |
Specifies the number of GET requests made to all buckets and objects in the buckets of a region. Unit: count |
≥ 0 counts |
Bucket |
1 minute |
|
put_request_count |
PUT Requests |
Specifies the number of PUT requests made to all buckets and objects in the buckets of a region. Unit: count |
≥ 0 counts |
Bucket |
1 minute |
|
first_byte_latency |
First Byte Download Delay |
Specifies the average time from receiving a GET request to the time that the system starts to respond in a measurement period. Unit: millisecond |
≥ 0 ms |
Bucket |
1 minute |
|
request_count_4xx |
4XX Status Codes |
Specifies the number of requests whose status code returned by the server is 4XX. Unit: count |
≥ 0 counts |
User Bucket API |
1 minute |
|
request_count_5xx |
5XX Status Codes |
Specifies the number of requests whose status code returned by the server is 5xx. Unit: count |
≥ 0 counts |
User Bucket API |
1 minute |
|
total_request_latency |
Average Request Latency |
Specifies the average time from receiving a request to the time that the system response ends in a measurement period. Unit: millisecond |
≥ 0 ms |
User Bucket API |
1 minute |
|
request_count_per_second |
Total TPS |
Average number of requests per second in a statistical period. Unit: count |
≥ 0 counts |
User Bucket Domain name |
1 minute |
|
request_count_get_per_second |
GET request TPS |
Average number of GET requests per second in a statistical period. Unit: count |
≥ 0 counts |
User Bucket Domain name |
1 minute |
|
request_count_put_per_second |
PUT request TPS |
Average number of PUT requests per second in a statistical period. Unit: count |
≥ 0 counts |
User Bucket Domain name |
1 minute |
|
request_count_delete_per_second |
DELETE request TPS |
Average number of DELETE requests per second in a statistical period. Unit: count |
≥ 0 counts |
User Bucket Domain name |
1 minute |
|
request_success_rate |
Request success rate |
This metric is used to measure the availability of the storage service system. It refers to the percentage of non-server error requests (with status code 5xx returned) in the total request count. It is calculated as follows: 1–5xx requests/Total requests x 100% Unit: % |
≥ 0, ≤ 100 |
User Bucket API Domain name |
1 minute |
|
effective_request_rate |
Valid request rate |
This metric measures the validity of client requests. Percentage of the valid requests in the total requests. It is calculated as follows: Number of client requests whose returned status code is 2xx or 3xx/Total number of requests x 100% Unit: % |
≥ 0, ≤ 100 |
User Bucket API |
1 minute |
|
request_break_rate |
Request interruption rate |
This metric measures the ratio of request failures caused by client interruption. It is calculated as follows: Number of client interrupted requests/Total number of requests x 100% Unit: % |
≥ 0, ≤ 100 |
User Bucket API |
1 minute |
|
request_code_count |
HTTP status code count |
This metric calculates the number of requests with error status codes returned by the server. For details, see Table 5. Unit: count |
≥ 0 counts |
Bucket API HTTP status code |
1 minute |
|
api_request_count_per_second |
API request TPS |
Average number of specific API requests sent to all buckets and objects of a tenant per second within a statistical period. Table 4 lists the types APIs that are supported. |
≥ 0 counts |
Bucket API |
1 minute |
|
request_count_monitor_2XX |
2xx Status Codes |
Specifies the count of server responses to requests whose status codes are 2xx. Unit: count |
≥ 0 counts |
User Bucket Domain name |
1 minute |
|
request_count_monitor_3XX |
3xx Status Codes |
Specifies the count of server responses to requests whose status codes are 3xx. Unit: count |
≥ 0 counts |
User Bucket Domain name |
1 minute |
|
Metric ID |
Metric |
Description |
Value Range |
Measurement Object & Dimension |
Monitoring Period (Original Metric) |
|---|---|---|---|---|---|
|
capacity_total |
Used storage space |
This metric measures storage space occupied by all data. Unit: byte |
≥ 0 bytes |
User Bucket |
30 minutes |
|
capacity_standard |
Used Standard storage space |
This metric measures Standard storage space occupied by all data. Unit: byte |
≥ 0 bytes |
User Bucket |
30 minutes |
|
capacity_infrequent_access |
Used Infrequent Access storage space |
This metric measures Infrequent Access storage space occupied by all data. Unit: byte |
≥ 0 bytes |
User Bucket |
30 minutes |
|
capacity_archive |
Used Archive storage space |
This metric measures Archive storage space occupied by all data. Unit: byte |
≥ 0 bytes |
User Bucket |
30 minutes |
|
object_num_all |
Total number of objects |
This metric measures total number of objects stored in all storage classes, including folders and files of all versions. Unit: count |
≥ 0 |
User Bucket |
30 minutes |
|
object_num_standard_total |
Number of objects in Standard storage |
This metric measures total number of objects stored in the Standard storage class, including folders and files of all versions. Unit: count |
≥ 0 |
User Bucket |
30 minutes |
|
object_num_infrequent_access_total |
Number of objects in Infrequent Access storage |
This metric measures total number of objects stored in the Infrequent Access storage class, including folders and files of all versions. Unit: count |
≥ 0 |
User Bucket |
30 minutes |
|
object_num_archive_total |
Number of objects in Archive storage |
This metric measures total number of objects stored in the Archive storage class, including folders and files of all versions. Unit: count |
≥ 0 |
User Bucket |
30 minutes |
Dimensions
The following dimensions (tenant ID, API name, domain name, and HTTP code) are available only in the CN North-Beijing1, CN North-Beijing4, CN East-Shanghai1, CN East-Shanghai2, CN Southwest-Guiyang1, CN South-Guangzhou, CN-Hong Kong, AP-Bangkok, AP-Singapore, and AF-Johannesburg regions.
|
Key |
Value |
|---|---|
|
tenant_id |
User dimension. The value is the Domain ID. |
|
bucket_name |
Bucket dimension. The value is the bucket name. |
|
api_name |
API dimension. For details about the value, see Table 4. |
|
domain_name |
Domain name dimension. The value is the domain name of the bucket to be accessed. |
|
http_code |
HTTP return code dimension. For details about the values, see Table 5. |
Request APIs
Table 3 lists the APIs supported by the api_name dimension:
|
ID |
Name |
|---|---|
|
LIST.BUCKETS |
Listing buckets |
|
PUT.BUCKET |
Creating buckets |
|
LIST.BUCKET.OBJECTS |
Listing objects in a bucket |
|
LIST.BUCKET.OBJECTVERSIONS |
Listing objects in a bucket (versioning) |
|
HEAD.BUCKET |
Obtaining bucket metadata |
|
GET.BUCKET.LOCATION |
Obtaining a bucket location |
|
LIST.BUCKET.UPLOADS |
Lists multipart uploads |
|
POST.OBJECT.MULTIDELETE |
Deleting objects in a batch |
|
LIST.BUCKET.OBJECTS |
Listing objects |
|
POST.OBJECT |
Uploading objects (POST) |
|
PUT.PART |
Uploading parts |
|
PUT.PART.COPY |
Copying parts |
|
DELETE.UPLOAD |
Canceling parts |
|
LIST.OBJECT.UPLOAD |
Listing uploaded parts |
|
POST.UPLOAD.COMPLETE |
Merging parts |
|
POST.UPLOAD.INIT |
Initializing multipart tasks |
|
PUT.OBJECT/QINIU.UPLOAD |
Uploading objects (Compatible with Qiniu APIs) |
|
APPEND.OBJECT/ |
Appending objects |
|
PUT.OBJECT.COPY/ QINIU.COPY |
Copying objects (Compatible with Qiniu APIs) |
|
DELETE.OBJECT/ QINIU.DELETE |
Deleting objects (Compatible with Qiniu APIs) |
|
GET.OBJECT/ QINIU.GET.OBJECT |
Downloading objects (Compatible with Qiniu APIs) |
|
HEAD.OBJECT/ QINIU.HEAD.OBJECT |
Heading objects (Compatible with Qiniu APIs) |
|
LIST.BUCKET.OBJECTVERSIONS |
Listing objects with versions |
|
POST.OBJECT.RESTORE |
Restoring objects |
|
PUT.OBJECT.METADATA |
Modifying object metadata |
|
QINIU.PUT.BASE64 |
Uploading Base64 encoded objects (Compatible with Qiniu APIs) |
|
QINIU.MAKE.BLOCK |
Creating blocks (Compatible with Qiniu APIs) |
|
QINIU.B.PUT |
Uploading blocks (Compatible with Qiniu APIs) |
|
QINIU.MAKE.FILE |
Creating objects (Compatible with Qiniu APIs) |
|
QINIU.MOVE |
Moving objects (Compatible with Qiniu APIs) |
|
QINIU.STAT |
Collecting object statistics (Compatible with Qiniu APIs) |
HTTP Status Codes
Table 3 lists the HTTP status codes supported by http_code dimension.
|
HTTP Status Code |
Description |
|---|---|
|
400 |
Incorrect request packet format. |
|
401 |
Failed to authenticate and authorize. |
|
403 |
Insufficient permission, access denied, limited MimeType, file type not allowed, or others |
|
404 |
The requested resource does not exist. |
|
405 |
The specified method is not allowed against the requested resource. |
|
406 |
CRC32 check failed for the uploaded data. |
|
413 |
Incorrect size of the uploaded object. |
|
579 |
The object is successfully uploaded, but the callback fails. |
|
599 |
The server fails to operate. |
|
612 |
The specified resource does not exist or has been deleted. |
|
614 |
The target resources already exist. |
|
701 |
The block expires, the segments are discontinuous, the total block size does not match the object size, or others. |
Last Article: Monitoring OBS
Next Article: Cloud Trace Service
Did this article solve your problem?
Thank you for your score！Your feedback would help us improve the website.