OperateLogHub - AnalyticDB - Alibaba Cloud Documentation Center

Modifies a LogHub delivery rule.

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

adb:OperateLogHub

update

DBCluster

acs:adb:{#regionId}:{#accountId}:dbcluster/{#DBClusterId}

None

Request parameters

Parameter	Type	Required	Description	Example
Create	boolean	Yes	Specifies whether to create the rule.	true
DBClusterId	string	Yes	The cluster ID. Note You can call the DescribeDBClusters operation to query the IDs of AnalyticDB for MySQL clusters in your account.	am-uf6rtqaj25491628z
ProjectName	string	Yes	The name of the Simple Log Service project.	test-adb
LogStoreName	string	Yes	The name of the Simple Log Service (SLS) Logstore.	beta-game-mjxb-ham-pool-export
DeliverName	string	Yes	The delivery name.	xhxsblz_limited_gift_pay
DeliverTime	string	Yes	The delivery time.	2024-10-24'T'13:10'Z'
Description	string	Yes	The description.	test
SchemaName	string	Yes	The database name.	wddata
TableName	string	Yes	The table name.	rest_action_latest
UserName	string	Yes	The username.	admin
Password	string	Yes	The password.	ads_123
FilterDirtyData	boolean	No	Specifies whether to filter dirty data. Valid values: true : true false : false	false
Provider	string	No	The provider.	SLS
LogHubStores	array<object>	Yes	An array of field mappings.
	object	No	The field mapping.
LogKey	string	Yes	The log keyword.	testKey
FieldKey	string	Yes	The value that corresponds to the keyword.	testValue

Response elements

Element	Type	Description	Example
	object
RequestId	string	The request ID.	71B41FF9-1275-5F75-973D-8BC3C60236E6

Examples

Success response

JSON format

{
  "RequestId": "71B41FF9-1275-5F75-973D-8BC3C60236E6"
}

Error codes

HTTP status code	Error code	Error message	Description
400	InvokeSLSException	An exception occured while invoke SLS Service.
404	InvalidDBCluster.NotFound	The DBClusterId provided does not exist in our records.	The specified DBClusterId parameter does not exist. Make sure that the DBClusterId value is valid.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.