- 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
Show all
Modifying a Group
Scenarios
After a group is created, you can modify its parameters by performing the following operations.
Modifying a Group
- Log in to COC.
- In the navigation pane, choose Resources > Application and Resource Management.
- Click Applications in the upper left corner.
- In the application column on the left, expand the application, select a component, and click
.
- Set parameters for modifying a group.
Table 1 Parameters for modifying a group Parameter
Description
Example Value
Group
Customize a group name based on the naming rule.
Test Group
Resource Association Method
Select a resource association mode.
- Manual association: You can manually associate resources with the group you created for unified management.
- Automatic association: You can add all resources with the same tag in an enterprise project to a resource group.
Manual association
Region
Select a region from the drop-down list.
-
Enterprise Project
This parameter is required only when Association Mode is set to Intelligent Association.
Select an enterprise project from the drop-down list.
-
Tag Key
This parameter is required only when Association Mode is set to Intelligent Association.
Enter the tag key of the target instance.
testKey
Tag Value
This parameter is required only when association mode is set to Automatic association.
Optional. Enter the tag value of the target instance.
testValue
Associate APM Environment
Optional. Configure the application, component, and environment of the APM service corresponding to the group. APM service performance information can be obtained through this field during fault diagnosis.
-
- Click OK.
The group is modified.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.