All Products
Search
Document Center

Server Load Balancer:EnableHighDefinationMonitor

Last Updated:Sep 20, 2024

Enables fine-grained monitoring for the current region.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

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.
OperationAccess levelResource typeCondition keyAssociated operation
slb:EnableHighDefinationMonitorcreate
  • All Resources
    *
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
TagsstringNo

The tags of the logs. The tags must be key-value pairs that are contained in a JSON dictionary.

[{"tagKey":"Key1","tagValue":"Value1"}]
RegionIdstringYes

The ID of the region where the Classic Load Balancer (CLB) instance is deployed.

You can call the DescribeRegions operation to query the most recent region list.

cn-hangzhou
LogProjectstringYes

The name of the project of Log Service. The name must be 4 to 63 characters in length, and can contain digits and lowercase letters. It must start and end with a digit or a letter.

my-project
LogStorestringYes

The name of the Logstore of Log Service. The name must be 2 to 64 characters in length and can contain digits, lowercase letters, hyphens (-) and underscores (_). It must start and end with a digit or a letter.

my-log-store

Response parameters

ParameterTypeDescriptionExample
object
Successstring

Indicates whether the call is successful. Valid values:

  • true: yes
  • false: no
true
RequestIdstring

The ID of the request.

2F398FF5-B349-5C01-8638-8E9A0BF1DBE6

Examples

Sample success responses

JSONformat

{
  "Success": "true",
  "RequestId": "2F398FF5-B349-5C01-8638-8E9A0BF1DBE6"
}

Error codes

HTTP status codeError codeError message
400OperationNotAllowed.HighDefinitionMonitorEnabledThe operation is not allowed because HighDefinitionMonitor is already enabled in this region.
400UnsupportedFeature.UserThe feature of HighDefinationMonitor is not supported.
400NoPermission.AliyunServiceRoleForSlbLogDeliveryYou are not authorized to create the service linked role. Role Name: AliyunServiceRoleForSlbLogDelivery. Service Name: logdelivery.slb.aliyuncs.com. Please ensure the user has been granted the ram:CreateServiceLinkedRole permission

For a list of error codes, visit the Service error codes.