This topic describes how to report custom events by sending an HTTP request.


  • Public endpoint:
  • The following table describes the internal endpoints in different regions.
    Region Region ID Endpoint
    China (Hangzhou) cn-hangzhou
    China (Zhangjiakou) cn-zhangjiakou
    China (Shanghai) cn-shanghai
    China (Beijing) cn-beijing
    China (Qingdao) cn-qingdao
    China (Shenzhen) cn-shenzhen
    China (Hong Kong) cn-hongkong
    China (Hohhot) cn-huhehaote
    UAE (Dubai) me-east-1
    US (Silicon Valley) us-west-1
    US (Virginia) us-east-1
    Japan (Tokyo) ap-northeast-1
    Germany (Frankfurt) eu-central-1
    Australia (Sydney) ap-southeast-2
    Singapore ap-southeast-1
    Malaysia (Kuala Lumpur) ap-southeast-3
    India (Mumbai) ap-south-1

Request syntax

An HTTP request for reporting custom events is in the following syntax:
POST /event/custom/upload HTTP/1.1 
Content-Length:<Content Length>
Content-MD5:<Content MD5>
Date:<GMT Date>

Request parameters

The following tables describe the headers and parameters in an HTTP request for reporting custom events.
  • Request headers
    Header Type Description
    Authorization String The authorization string, in the format of AccessKeyId:SignString.
    Content-Length Numeric value The length of the HTTP request body, as defined in RFC 2616. This header is only required when the request has a body.
    Content-MD5 String The MD5 value of the HTTP request body. The MD5 value is a string consisting of uppercase letters and digits. This header is only required when the request has a body.
    Content-Type String The type of the content that is sent in the HTTP request. Set the value to application/json.
    Date String The standard timestamp header of the HTTP request. This timestamp header follows the RFC 1123 time format and uses the GMT standard time.

    Example: Mon, 3 Jan 2010 08:33:47 GMT.

    Host string The full hostname of the HTTP request. This header does not include the protocol header such as https://.


    x-cms-api-version string The version of the API. Set the value to 1.0.
    x-cms-signature string The signature algorithm to use. CloudMonitor only supports the HMAC-SHA1 signature algorithm. For more information, see Does CloudMonitor support the HMAC-SHA1 signature algorithm and how do I use it?.
    x-cms-ip string The IP address of the host that reports the custom events.
    User-Agent String The description of the client.
  • Request parameters
    Parameter Type Required Description
    content String Yes The details of the event.
    name String Yes The name of the event.
    groupId Numeric value No The ID of the application group to which the event belongs.
    time String No The time when the event occurred.

Sample success response

The following content shows the sample response to an HTTP request for reporting custom events:

  "code":"200",// The HTTP status code 200 indicates that the request was successful.
  "msg":""// The value is empty when the events are reported.