All Products
Search
Document Center

Simple Log Service:TagResources

Last Updated:Nov 13, 2024

Creates and adds tags to a resource. You can add tags only to projects.

Operation description

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 Resource Access Management (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.

ActionResource
log:TagResourcesThe resource format varies based on 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

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

Authorization information

There is currently no authorization information disclosed in the API.

Request syntax

POST /tag HTTP/1.1

Request parameters

ParameterTypeRequiredDescriptionExample
bodyobjectYes

The request struct.

resourceTypestringYes

The type of the resource. Valid values:

  • project
  • logstore
  • dashboard
  • machinegroup
  • logtailconfig
project
resourceIdarrayYes

The resource IDs. You can specify only one resource and add tags to the resource.

stringNo

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
ali-test-project
tagsarray<object>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.

objectNo
keystringYes

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.
key1
valuestringYes

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://.
value1

Response parameters

ParameterTypeDescriptionExample
headersobject
Serverstring

The name of the server.

nginx
Content-Typestring

The content type of the response body.

application/json
Content-Lengthstring

The content length of the response body.

0
Connectionstring

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.
close
Datestring

The time when the response was returned.

Sun, 27 May 2018 08:25:04 GMT
x-log-requestidstring

The request ID.

5B0A6B60BB6EE39764D458B5

Examples

Sample success responses

JSONformat

{}

Error codes

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