Overview

COS data (such as traffic and the number of read/write requests) is collected and displayed according to Basic Cloud Monitor. Therefore, you can go to the COS or Cloud Monitor console to view COS monitoring data in detail.

Note：

This document describes how to obtain statistics in the COS console. You can call Cloud Monitor APIs to obtain more detailed data. For more information, please see Documentation of Cloud Monitor.

Basic Features

Cloud Monitor provides the following modules for COS to implement monitoring and alarming.

Use Cases

• Daily management: You can log in to the Cloud Monitor console to view the running status of COS in real time.
• Troubleshooting: You can receive alarm notifications when the data of a monitoring metric reaches the threshold. It allows you to quickly notify the exceptions, find out the causes, and fix the issues.

Setting and Querying via Console

You can create an alarm policy for COS in the Cloud Monitor console. If the data of a monitoring metric reaches the specified threshold, you will receive an alarm notification. For detailed directions, please see Setting Monitoring Alarms.

You can go to Cloud Product Monitoring > Cloud Object Storage to view the COS monitoring data (including the monitoring data of all buckets, health status, number of alarm policies, and more). Alternatively, you can go to the COS console to view the data. For detailed directions, please see Viewing Data Overview and Querying Monitoring Data.

Querying Monitoring Data via APIs

You can call the corresponding APIs to view the COS monitoring data. The monitoring metrics are described below. For more information about the monitoring APIs, please see COS Monitoring Metrics.

Monitoring Metrics

Note：

COS uses a generic region. Therefore, select "Guangzhou" for Region when you pull COS monitoring metric data, regardless of where the bucket resides.

• When pulling data using API Explorer, select "ap-guangzhou" for the Region field.
• When pulling data using an SDK, enter "ap-guangzhou" for the Region field.

Request metrics

Storage metrics

Traffic metrics

Return code metrics

Note：

1. For more information about 3xx, 4xx, and 5xx status codes, please see Error Codes.
2. The statistical granularity (period) may vary by metric. You can call the DescribeBaseMetrics API to obtain the period supported by each metric.

Data retrieval metrics

Dimension Parameters

Input Parameters

To query COS monitoring data, the values of the input parameters are as follows:

&Namespace=QCE/COS
&Instances.N.Dimensions.0.Name=appid
&Instances.N.Dimensions.0.Value=root account APPID
&Instances.N.Dimensions.1.Name=bucket
&Instances.N.Dimensions.1.Value=bucket name

Monitoring Description

• Monitoring interval: Cloud Monitor supports multiple monitoring intervals, including monitoring data in real time, in the past 24 hours, in the past 7 days, and in the user-specified period, with time granularity of 1 minute, 5 minutes, 1 hour, and 1 day.
• Data storage: 1-minute monitoring data can be stored for 15 days, 5-minute monitoring data for 31 days, 1-hour data for 93 days, and 1-day monitoring data for 186 days.
• Alarm display: Cloud Monitor integrates the monitoring data of COS and displays the data in graphs. Alarm notifications can be sent to you according to the predefined alarm metrics of your product. In this way, you can stay informed of the overall running status.
• Alarm settings: You can set the threshold for the monitoring metrics. When the monitoring data meets the alarm condition that is set, Cloud Monitor will send the alarm notifications to the specified users. For more information, please see Cloud Monitor Overview and Setting Monitoring Alarms.