CMDB Naming conventions

This specification is formulated to ensure that the underlying data, such as system name, app name, SLB name, ECS name, and so on, is standardized in the CMDB.

1, the name can only be composed of letters and numbers, not with underscores, dots and other special characters.

For example: Appfinweb, Appsendmessageservice, AppAdmin2 are the correct naming methods. Fin_web, Fin.web is the wrong naming method.

2, the first letter to uppercase, if there are multiple words in the name, then all the first letter of the word should be capitalized.

For example: Host, Host01, zabbixserver are the correct naming methods. Host, Zabbixserver, and Zabbixserver are named in the wrong way.

3. If the name has an abbreviation in English, the name needs to be capitalized.

For example: UAT, UBT, SLB, API, Slbuat, Slbredis are the correct naming methods. Uat, uat01, apiserver, etc. are the wrong naming methods.

4. Naming of System, APP, SLB, ECS

system naming Specification : All system except Chinese name, must carry alias, alias all start with "Sys", for example Sysfin,sysdriverservice and so on.

App name specification : All app names start with "app", Front end with Web, backend with service, such as Appfinweb,appsendmessageservice, etc.

SLB Name specification: all SLB names start with "SLB", for example:slbblacklist, Slbsendmessageservice, etc.

tag Name Specification : All tags are named from the associated information on the ECS, if the app is associated with Appfinweb, it will automatically add the app name and the system to which it belongs, the SLB of ECS as its tag name

ECS Name specification: all ECS names start with "ECS", followed by a 4-digit serial number, for example: ECS0001, ECS0002, etc.

The dimensions and levels of the tag

Dimension of	Team	Environment	System	SLB	App	Other
Level	1	2	3	4	5	6

This article from "Zengestudy" blog, declined reprint!

CMDB Naming conventions