Stops live monitoring.
Operation description
Before you call this operation to stop live monitoring, make sure that live monitoring is started. You must call the CreateLiveStreamMonitor operation to create a monitoring session, obtain the MonitorId value from the response parameters, and then start live monitoring.
QPS limits
You can call this operation up to 10 times per second per account. If the number of the calls per second exceeds the limit, throttling is triggered. As a result, your business may be affected. We recommend that you take note of the limit when you call this operation. For more information, see QPS limit on an API operation in ApsaraVideo Live.
Debugging
Authorization information
The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action
policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:
- Operation: the value that you can use in the Action element to specify the operation on a resource.
- Access level: the access level of each operation. The levels are read, write, and list.
- Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level,
All Resources
is used in the Resource type column of the operation.
- Condition Key: the condition key that is defined by the cloud service.
- Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
Operation | Access level | Resource type | Condition key | Associated operation |
---|---|---|---|---|
live:StopLiveStreamMonitor | update | *All Resources * |
| none |
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
MonitorId | string | Yes | The ID of the monitoring session. Note
To obtain the MonitorId value, call the CreateLiveStreamMonitor operation.
| 445409ec-7eaa-461d-8f29-4bec2eb9**** |
Response parameters
Examples
Sample success responses
JSON
format
{
"RequestId": "5c6a2a0d-f228-4a64-af62-20e91b9676b3"
}
Error codes
HTTP status code | Error code | Error message |
---|---|---|
400 | InvalidUserId.Malformed | %s |
400 | InvalidMonitorId.Malformed | %s |
400 | StreamMonitorAlreadyStop | %s |
401 | IllegalOperation | %s |
403 | UserQuotaExceed | %s |
404 | StreamMonitorNotExist | %s |
500 | InternalError | %s |
For a list of error codes, visit the Service error codes.