Cloud Operations Center
Cloud Operations Center
- Service Overview
- Getting Started
-
User Guide
- COC Enablement and Permissions Granting
- Overview
-
Application and Resource Management
- Resource Management
-
Application Management
- Creating an Application
- Modifying an Application
- Deleting an Application
- Editing an Application Topology
- Creating a Component
- Modifying a Component
- Deleted a Component
- Creating a Group
- Modifying a Group
- Deleting a Group
- Manually Associating Resources with a Group
- Intelligently Associating Resources with a Group
- Transferring Resources
- Disassociating a Resource from an Application Group
- Viewing Resource Details
- Viewing Capacity Rankings
- Multi-cloud Configurations
- Cross-Account Resources
- Resource O&M
- Automated O&M
- Faults
- 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
- General Reference
On this page
Show all
Help Center/
Cloud Operations Center/
User Guide/
Basic Configurations/
Process Management/
Incident Handling Process/
Reviewing an Incident
Copied.
Reviewing an Incident
- Log in to COC.
- In the navigation pane on the left, choose Basic Configurations > Process Management. Click the Incident Review tab under Incident Process to configure the incident deescalation and suspension review processes. By default, incident deescalation does not need to be reviewed, and incident suspension is not available.
Figure 1 Reviewing an incident
- Click Create Incident Review to configure the incident deescalation or suspension process, and specify the incident process configurations, incident level, and review configurations.
Figure 2 Creating an incident review process
- After the configuration is complete, the incident deescalation needs to be reviewed on the incidents processing page. In addition, the incident can be suspended.
Figure 3 Incident processing page
NOTICE:
1. The created incident ticket process takes effect only after the incident deescalation and review process configurations take effect.
2. Incidents in the handled state can be escalated, deescalated, or suspended.
3. Before closing an incident, close the escalation, deescalation, and suspension e-flows.
4. Incident escalation does not need to be reviewed.
Parent topic: Incident Handling Process
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot