TagResources - Simple Log Service - Alibaba Cloud Documentation Center

Usage notes

Host consists of a project name and a Simple Log Service endpoint. You must specify a project in Host.
An AccessKey pair is created and obtained. For more information, see AccessKey pair.

The AccessKey pair of an Alibaba Cloud account has permissions on all API operations. Using these credentials to perform operations in Simple Log Service is a high-risk operation. We recommend that you use a RAM user to call API operations or perform routine O&M. To create a RAM user, log on to the RAM console. Make sure that the RAM user has the management permissions on Simple Log Service resources. For more information, see Create a RAM user and authorize the RAM user to access Simple Log Service.
The information that is required to query logs is obtained. The information includes the name of the project to which the logs belong and the region of the project. For more information, see Manage a project.
For more information, see Authorization rules. The following types of resources are supported: project, Logstore, dashboard, machine group, and Logtail configuration.

Authentication resources

The following table describes the authorization information that is required for this operation. You can add the information to the Action element of a RAM policy statement to grant a RAM user or a RAM role the permissions to call this operation.

Action	Resource
`log:TagResources`	The resource format varies with the resource type. -`acs:log:{#regionId}:{#accountId}:project/{#ProjectName}` -`acs:log:${regionName}:${accountId}:project/${projectName}/logstore/${logstoreName}` -`acs:log:${regionName}:${accountId}:project/${projectName}/dashboard/${dashboardName}` -`acs:log:${regionName}:${accountId}:project/${projectName}/machinegroup/${machineGroupName}` -`acs:log:${regionName}:${accountId}:project/${projectName}/logtailconfig/${logtailConfigName}`

Action

Resource

log:TagResources

The resource format varies with the resource type.

-acs:log:{#regionId}:{#accountId}:project/{#ProjectName}

-acs:log:${regionName}:${accountId}:project/${projectName}/logstore/${logstoreName}

-acs:log:${regionName}:${accountId}:project/${projectName}/dashboard/${dashboardName}

-acs:log:${regionName}:${accountId}:project/${projectName}/machinegroup/${machineGroupName}

-acs:log:${regionName}:${accountId}:project/${projectName}/logtailconfig/${logtailConfigName}

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer. OpenAPI Explorer dynamically generates the sample code of the operation for different SDKs.

Request headers

This operation uses only common request headers and does not have operation-specific request headers. For more information, see Common request parameters.

Request syntax

POST /tag HTTP/1.1

Request parameters

Parameter	Type	Position	Required	Example	Description
	Object	Body	Yes		The request struct.
resourceType	String	Body	Yes	project	The type of the resource. Valid values: project logstore dashboard MachineGroup LogtailConfig
resourceId	Array of String	Body	Yes	ali-test-project	The resource ID. In this example, a Logstore is used. projectName indicates the project name. # is used to concatenate strings. logstore indicates the Logstore name. project: projectName logstore: projectName#logstore dashboard: projectName#dashboard MachineGroup: projectName#MachineGroup LogtailConfig: projectName#LogtailConfig
tags	Array	Body	Yes		The tags that you want to add to the resource. You can specify up to 20 tags in each call. Each tag is a key-value pair.
key	String	Body	Yes	key1	The key of the tag. The key must meet the following requirements: The key must be `1 to 128` characters in length. The key cannot contain `http://` or `https://`. The key cannot start with `acs:` or `aliyun`.
value	String	Body	Yes	value1	The value of the tag. The value must meet the following requirements: The value must be `1 to 128` characters in length. The value cannot contain `http://` or `https://`.

Response parameters

Parameter	Type	Example	Description
Server	String	nginx	The name of the server.
Content-Type	String	application/json	The format of the response body.
Content-Length	String	0	The length of the response body.
Connection	String	close	Indicates whether the connection is persistent. Valid values: close: The connection is non-persistent. A new TCP connection is established for each HTTP request. keep-alive: The connection is persistent. After a TCP connection is established, the connection remains open, and no more time or bandwidth is consumed to establish new connections.
Date	String	Sun, 27 May 2018 08:25:04 GMT	The time when the response was returned.
x-log-requestid	String	5B0A6B60BB6EE39764D458B5	The request ID.

Examples

Sample requests

POST /tag HTTP/1.1
Host:ali-test-project.cn-hangzhou.log.aliyuncs.com
Content-Type:application/json

{
  "resourceType" : "project",
  "resourceId" : [ "ali-test-project" ],
  "tags" : [ {
    "key" : "key1",
    "value" : "value1"
  } ]
}

Sample success responses

JSON format

HTTP/1.1 200 OK

Error codes

For a list of error codes, see Service error codes.