Request structure

CloudMonitor APIs are RPC APIs. You can call CloudMonitor APIs by sending HTTP requests.

The request structure is as follows:



  • Endpoint: the cloud service access point. The endpoint of CloudMonitor is For more information about the endpoints of various regions, see CloudMonitor endpoints.
  • Action: the operation that you want to perform. For example, you can call DescribeMetricList to query the monitoring data of an instance.
  • Version: the version of the APIs that you want to use. The current CloudMonitor API version is 2019-01-01.
  • Parameters: the request parameters separated with ampersands (&). Request parameters consist of common request parameters and custom API parameters. Common request parameters include the API version number, authentication information, and other information.

The following example shows how to call DescribeMetricList to query the monitoring data of an instance.

CloudMonitor endpoints

Region Endpoint
China (Hangzhou)
China (Shanghai)
China (Qingdao)
China (Beijing)
China (Shenzhen)
China (Zhangjiakou-Beijing Winter Olympics)
China (Hong Kong)
US (Silicon Valley)
US (Virginia)
Germany (Frankfurt)
Australia (Sydney)
UAE (Dubai)
Japan (Tokyo)
Malaysia (Kuala Lumpur)
China (Hohhot)
Indonesia (Jakarta)
India (Mumbai)
UK (London)

API authorization

To keep your account secure, we recommend that you call CloudMonitor APIs as a RAM user. Before calling CloudMonitor APIs as a RAM user, you must create a RAM user and assign corresponding permissions to it.

API signature

To ensure secure, Alibaba Cloud authenticates each API request through the signature. When you manually make an API request, you must use your AccessKey Secret to calculate the HMAC value based on the encoded and sorted request string in accordance with the definition in RFC 2104. The HMAC value is the signature. For more information, see Sign RPC APIs.

For an RPC API, you must add the signature to the API request in the following format:


Take DescribeMetricList as an example. The AccessKey ID is testid and AccessKey Secret is testsecret. The original request URL is as follows:{instanceId:'i-abcdefgh123456'}&Timestamp=2017-03-23T06:59:55Z&Namespace=acs_ecs_dashboard&SignatureVersion=1.0&Format=JSON&SignatureNonce=aeb03861-611f-43c6-9c07-b752fad3dc06&Version=2015-10-20&AccessKeyId=TestId&MetricName=cpu_idle&SignatureMethod=HMAC-SHA1
The corresponding StringToSign is as follows:
AccessKey Secret is testsecret, so the key used for HMAC calculation is testsecret& and the calculated signature value is as follows:

Add the signature value as the Signature parameter to the request URL. The final URL is as follows: