Docs

Transit Router

Projects and Tags

Tag management

Overview

Tags identify resources and help you mark and categorize resources with similar characteristics from different dimensions (such as purpose, type, owner, or environment). This makes it easy to quickly find Transit Router (TR) resources with specific tags, filter related resource bills by tags, and implement cost allocation management.

Application scenarios

Group management

You can associate different tags with different environments (such as the production environment and test environment), different operating systems (such as Windows and Linux), or different client platforms (such as iOS and Android). For example, you can associate a tag with a certain key-value pair (such as Test:Server-Windows) with all instances involved in a test environment. During routine maintenance, you can filter a group of tagged instances from all instances and then perform actions.

Cost allocation with tags

In team or project management, you can add tags based on groups, projects, or departments (e.g., CostCenter:Project) to categorize resources. Then, use these tags in the Billing Center for cost allocation management. When using tags for cost allocation, you need to enable cost tags under Cost organization - Bill tags in the Billing Center console to apply the corresponding tags to bill details. For detailed instructions, see Bill tags.

Tag types

System tag: Tags that are automatically added to resources when they are created. System tags usually start with volc: or sys:, can only be viewed and cannot be edited.

Custom tag: Tags that are manually added to resources. Note that custom tags cannot start with volc: or sys: in any case variation.

For tag design principles, see Tag design principles.

Tag usage instructions

A tag consists of a tag key and a tag value, both of which are case-sensitive. Value can be empty.

Keys of multiple tags for the same instance must be unique, and each key can have only one value.

Resources that support tag management, including TR instances, network instance attachments, TR route tables, inter-region attachments, CEN bandwidth packages, and multicast domains.

tip

In cross-account scenarios, the recipient account can add tags to a shared TR instance after accepting it, independently of the tags added by the sharer account that owns the resource.

In cross-regions scenarios, you can add tags separately for the same inter-region attachment in different regions without affecting each other.

You can add up to 20 custom tags per operation and up to 50 custom tags per TR resource.

Tag actions

Edit a tag

For example, log in to the Transit Router console.

In the top menu bar, select the project and region to which the target TR instance belongs.

Hover over the number in the tag column of the target TR instance, then click the edit icon.

Edit the tag.

Add a tag: Enter new tag keys and values as needed.

Modify a tag: Modify the key and value of an existing tag.

Delete a tag: Click the delete icon to the right of the target tag.

Click Save to complete the action.

Search instances by tags

Instructions

Supports searching with multiple tags simultaneously. A maximum of 10 tags can be added in a single operation.

If there are multiple tags in the search box, the relationship between the keys of these tags is logical AND. If the same key has multiple values, the relationship between these values is a logical OR.

During a search, you can leave value blank or empty. Leaving it blank indicates no restrictions on values; while an empty value indicates searching for tags with empty values.

During a search, you can add up to three values for a single key.

tip

Since different cloud resource instances can share the same tag key but have different tag values, you may encounter scenarios where multiple values are added for the same tag key during searches.

Example

Search for cloud resource instances based on tags. Assume that the search conditions are as follows:

Tag 1: Keys: key1; Values: value1, value2.

Tag 2: Key: key2; Values: no specified values.

The cloud resource instances listed in the result must meet all of the following conditions:

It contains both key1 and key2.

For a tag with key1, its value can be value1 or value2.

For a tag with key2, its value can be any value.

Procedure

For example, log in to the Transit Router console.

Select the project and region of the target TR instance in the top navigation bar.

In the Tag column, click the filter icon.

Select or type keys and values of tags.

tip

You can add up to 10 keys and configure up to three values for each key in a search.

The relationship among the specified keys is logical AND, and the relationship among multiple values of the same key is logical OR.

Click Apply to search for target resources.

Accounting by tags

For details, see Bill tags.