Overview
The tag-splitting feature allows for the allocation and recording of transaction expenditures of the execution resource group costs in WeData according to pre-defined tags. By utilizing the tag-splitting feature, it is easier to manage and analyze the billing budget for WeData and conduct cost analysis.
WeData Execution Resource Group Binding Tag
The feature of binding tags to WeData supports only root accounts and sub-accounts with payment permissions (CAM control) and is unavailable for other users.
The root account by default has the permission to configure tags, while sub-accounts need to be configured in CAM.
In the policy configuration, you can find the QCloudFinanceFullAccess policy and associate it with the users who require authorization for the tag-binding feature, thus granting the corresponding users to bind editions and resource groups by using tag binding.
To operate the tag feature, the sub-account must be associated with the QCloudFinanceFullAccess policy.
Preliminary Work: Add Permissions
1. Click to enter CAM.
2. Click Policies, search for the QCloudFinanceFullAccess policy, and click Associate Users/Groups/Roles.
3. Select the users to be added.
4. Policy association succeeded.
Step 1: Tag the Execution Resource Group
Enter the WeData console page. There are two ways to tag. One is tagging directly during resource purchase, and another is after the resource group is created successfully, configuring tags for scheduling resource group and integrating resource group in the execution resource group page.
Bind in the Execution Resource Group Purchase Page
When purchasing WeData edition and execution resource groups, you can also directly add tags to resources.
Add a Tag when purchasing a Resource Group
Bind in the Execution Resource Group Purchase Page
Scheduling Resource Group
In the Scheduling Resource Group page, select the resource group to which you want to add a tag, and click Edit Tag in the operation column to add tags to the scheduling resource group.
Integrated Resource Group
In the Integrated Resource Group page, select the resource group that needs tags configured. Tags can be configured separately for offline packages and real-time packages by clicking Edit Tag in the operation column, to add tags to both types of packages.
Scheduling resource group and integrated resource group can also bind tags through batch feature.
Step 2: Set the Tag as a Cost Allocation Tag
1. Enter the Billing Center.
2. In the left menu, click Bill Tag under Billing Management.
3. In the Bill Tag page, check the tag keys for the WeData edition and resources that need cost allocation billing, and click Set as Bill Tag in the operation column.
Step 3: View Bill
After binding tags to the WeData edition and resources, and setting them as Bill Tag, you can view billing-related information by Bill Tag in the Billing Overview page. The bill data for the historical paid months remains unchanged.
Note:
If the resource was purchased the same day, the bill will sync the day after the bill tag is applied.
Appendix: Tag Management
Step 1: Enter the Tag Management Page
1. Log in to the WeData console.
2. In the search box above, type Tag and select Tag under Console Entrance from the drop-down list to enter the Tag page.
Step 2: Create Tag
1. On the Tag page, select Tag List from the left menu and click Create Tag.
2. In the Create Tag pop-up window, enter the tag information, including Tag key and Tag value.
Tag Key: Tag Key is a name used to describe or identify specific attributes or categories. It can be seen as a representation of a classification method or data attribute. For example, in cloud computing, a tag key can represent the type, environment, project, etc., of a resource. Each tag key should be unique and defined by users.
Tag Value: Tag Value is the specific value associated with a tag key. It provides a concrete instantiation of the attribute or category described by the tag key. For instance, for the Tag Key "environment," there could be different Tag Values such as "development," "test," and "production." Tag Value can be used to further segment and classify entities.
In this example, define one Tag Key and three Tag Values:
Tag Key: WeData.
Tag Values: user1, user2, user3.
3. After creating the Tag, the created Tag information can be seen in the Tag List.