Cloud Operations Center
Cloud Operations Center
- Service Overview
- Getting Started
-
User Guide
- COC Enablement and Permissions Granting
- Overview
-
Resources
- Resource Management
-
Application Management
- Overview
- Creating an Application
- Modifying an Application
- Deleting an Application
- Application Topology
- Creating a Component
- Modifying a Component
- Deleted a Component
- Creating a Group
- Modifying a Group
- Deleting a Group
- Manually Associating with Resources
- Automatically Associating with Resources
- Transferring Resources
- Disassociating Resources from an Application Group
- Viewing Resource Details
- Viewing Capacity Details
- Resource O&M
- Automated O&M
-
Faults
- Diagnosis Tools
- Alarms
-
Incident Management
- Incidents
- Creating an Incident
- Rejecting an Incident
- Resubmitting an Incident After Rejection
- Forwarding Incidents
- Handling Incidents
- Upgrading/Downgrading an Incident
- Adding Remarks
- Starting a War Room
- Handling an Incident
- Verifying Incident
- Creating an Improvement Ticket For An Incident
- Incident History
- WarRoom
- Improvement Management
- Issue Management
- Forwarding Rules
- Data Source Integration Management
- Change Management
- Resilience Center
- Task Management
- Basic Configurations
- Viewing Logs
- Best Practices
- API Reference
-
FAQs
- Product Consulting
- Resource Management FAQs
-
FAQs About Resource O&M
-
Patch Management FAQs
- What Can I Do If the Patch Baselines Do Not Take Effect?
- What Are the Differences Between the Installation Rule Baselines And User-defined Baselines?
- What Can I Do If Exception all mirrors were tried Is Recorded in the Patch Service Ticket Log?
- Why Can't I Select a Node?
- What Can I Do If the Compliance Report Still Reports Non-compliance for a Patch After the Patch Has Been Repaired?
- What Can I Do If the lsb_release not found Error Occurs During Patch Operations?
- Automation FAQs
- Batch Operation FAQs
- FAQs About Parameter Management
- Resource O&M Permissions and Supported Actions
-
Patch Management FAQs
- FAQs About Fault Management
- FAQs About Change Ticket Management
- Resilience Center FAQs
- Change History
On this page
Managing Tags
Updated on 2025-03-17 GMT+08:00
Scenarios
Tag Management Service (TMS) enables you to use tags on the management console to manage resources. TMS works with other cloud services to manage tags. TMS manages tags globally, and other cloud services manage their own tags. If you need to manage a lot of cloud resources, use TMS.
- You are advised to set pre-defined tags on the TMS console.
- A tag consists of a key and value. You can add only one value for each key.
- Each instance can have up to 10 tags.
Modifying a Tag
- Log in to COC.
- In the navigation pane, choose Resources > Application and Resource Management.
- Click
on the right of the filter column and select Label.
- Select the target instance, click
in the label column, and then click Tag Management.
Figure 1 Managing tags - Click Add Tag.
- When you enter a tag key and value, the system automatically displays all predefined tags associated with the current user.
- The tag key cannot start or end with a space, or start with _sys_. It can contain letters, digits, spaces, and the following special characters: _.:=+-@. A maximum of 128 characters are allowed.
- The tag key cannot start or end with a space. It can contain letters, digits, spaces, and the following special characters: _.:=+-@. A maximum of 256 characters are allowed.
You can modify an existing tag. Click the key or value of a tag and enter a new key or value.
- Click OK.
The tag is modified.
Deleting a Tag
- Log in to COC.
- In the navigation pane, choose Resources > Application and Resource Management.
- Click
on the right of the filter column and select Label.
- Select the target instance, click
in the label column, and then click Tag Management.
Figure 2 Managing tags - Select the tag to be deleted and click
.
- Click OK.
The tag is deleted.
Parent topic: Resource Management
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.