Principles for Naming Tags
Principles
After a company moves to the cloud, as cloud resources keep growing, they usually need to manage hundreds of thousands or millions of resources within one account. It is both difficult and inefficient to manually classify these resources. To meet this challenge head on, a cloud service that can enable automatic cloud management is required.
TMS enables you to classify and group resources with tags. You can tag resources by their attributes, such as by department, region, or project.
Use Standardized Tag Names
Classifying resources by using standardized tag names can facilitate automatic and efficient cloud management.
A standardized tag name should meet the following requirements:
- Use a consistent case, such as lower case or upper case, for all tag keys and values.
- If Chinese characters are used in a tag name, you are advised to limit the characters to six to avoid exceeding the upper limit.
Use Consistent and Concise Tag Names
You are advised to use consistent expression for the same attribute. For example, if "purpose" was used to indicate resource utility, you should avoid using other words, such as "use" or "object", to indicate resource utility.
Keep the tag keys and values clear and concise. Do not use a tag name to indicate more than one meaning.
Plan and predefine tags in advance
You can plan and predefine tags, especially tag keys, in parallel with resource planning. Then you can use the predefined tags to classify your resources.
Avoid containing privacy information
A tag name should avoid containing enterprise privacy information, such as names of confidential enterprise projects, project revenue information, phone numbers, or email addresses.
Examples
The following table lists some tag naming examples. You are advised to use lowercase letters for all tag keys and values.
Category |
Key |
Value |
---|---|---|
Organizational structure |
headquarters subcompany department team group |
Corresponding names |
Service architecture |
product module service microservice |
Corresponding names |
Roles |
role user |
network administrator audit administrator operational administrator development personnel test personnel |
Purpose |
purpose |
Corresponding utility |
Project and environment |
project task environment |
Project-related values |
Cost attribution |
costcenter businessunit |
Department-related costs |
Order |
order |
Order ID |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot