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
Help Center/
Cloud Operations Center/
User Guide/
Basic Configurations/
Shift Schedule Management/
Managing O&M Engineers
Managing O&M Engineers
Updated on 2025-03-17 GMT+08:00
You can query, modify, and delete O&M engineers in different shifts.
Scenarios
When the engineers in a schedule change, you can modify or delete the information about the changes. The method of changing the engineers varies according to the scenario.
Global Schedule of Fixed Shifts
- Log in to COC.
- In the navigation pane on the left, choose Basic Configurations > Shift Schedule Management. On the displayed page, select a scenario and a role, locate a schedule and click Delete in the Operation column.
Figure 1 Deleting an engineer
Global Schedule of Rotating Shifts
- Log in to COC.
- In the navigation pane, choose Basic Configuration > Shift Schedule Management. Select a scheduling scenario and click Clear.
Figure 2 Deleting engineers
- In the Clear drawer, enter the start time and end time, select a scheduling role, and click OK.
Figure 3 Clearing personnel from a schedule
Application-specific Schedule of Fixed Shifts
- Log in to COC.
- In the navigation pane on the left, choose Basic Configurations > Shift Schedule Management. On the displayed page, select a scenario, region, and applications, and click Modify in the Operation column to add or delete engineers.
Figure 4 Modifying a fixed shift
Application-specific Schedule of Rotating Shifts
- Log in to COC.
- In the navigation pane, choose Basic Configuration > Shift Schedule Management. Select a scheduling scenario and click Clear.
Figure 5 Clearing schedules
- In the Clear drawer, select regions and applications, enter the start time and end time, select scheduling roles, and click OK.
Figure 6 Clearing schedules
Parent topic: Shift Schedule 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.