All Products
Search
Document Center

Cloud Monitor:PutCustomEvent

Last Updated:Jan 23, 2026

Reports custom events.

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

Test

RAM authorization

The table below describes the authorization required to call this API. You can define it in a Resource Access Management (RAM) policy. The table's columns are detailed below:

  • Action: The actions can be used in the Action element of RAM permission policy statements to grant permissions to perform the operation.

  • API: The API that you can call to perform the action.

  • Access level: The predefined level of access granted for each API. Valid values: create, list, get, update, and delete.

  • Resource type: The type of the resource that supports authorization to perform the action. It indicates if the action supports resource-level permission. The specified resource must be compatible with the action. Otherwise, the policy will be ineffective.

    • For APIs with resource-level permissions, required resource types are marked with an asterisk (*). Specify the corresponding Alibaba Cloud Resource Name (ARN) in the Resource element of the policy.

    • For APIs without resource-level permissions, it is shown as All Resources. Use an asterisk (*) in the Resource element of the policy.

  • Condition key: The condition keys defined by the service. The key allows for granular control, applying to either actions alone or actions associated with specific resources. In addition to service-specific condition keys, Alibaba Cloud provides a set of common condition keys applicable across all RAM-supported services.

  • Dependent action: The dependent actions required to run the action. To complete the action, the RAM user or the RAM role must have the permissions to perform all dependent actions.

Action

Access level

Resource type

Condition key

Dependent action

cms:PutCustomEvent

create

*All Resource

*

None None

Request parameters

Parameter

Type

Required

Description

Example

EventInfo

array<object>

Yes

The event details.

object

No

EventName

string

Yes

The event name. Valid values of N: 1 to 50.

myEvent

Time

string

No

The time when the event occurred.

Format: yyyyMMddTHHmmss.SSSZ.

Valid values of N: 1 to 50.

Note

You can also specify a UNIX timestamp. Example: 1552199984000. Unit: milliseconds.

20171013T170923.456+0800

GroupId

string

No

The ID of the application group. Valid values of N: 1 to 50.

Default value: 0. This value indicates that the event to be reported does not belong to any application group.

123456

Content

string

Yes

The event content. Valid values of N: 1 to 50.

IOException

Response elements

Element

Type

Description

Example

object

Code

string

The responses code.

Note

The status code 200 indicates that the request was successful.

200

Message

string

The returned message.

success

RequestId

string

The request ID.

131DD9C8-9A32-4428-AD2E-4E3013B6E3A7

Examples

Success response

JSON format

{
  "Code": "200",
  "Message": "success",
  "RequestId": "131DD9C8-9A32-4428-AD2E-4E3013B6E3A7"
}

Error codes

HTTP status code

Error code

Error message

Description

400 %s %s
500 %s %s
500 InternalError The request processing has failed due to some unknown error.
403 %s %s
404 %s %s

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.