- 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
Copied.
Creating an Incident
Scenarios
Create an incident ticket using Cloud Operations Center.
Prerequisites
You have created an application by referring to Application Management.
Precautions
Create an incident service ticket.
Procedure
- Log in to COC.
- In the navigation pane, choose Fault Management > Incidents. On the displayed page, click Create.
Figure 1 Incident ticket list
- Enter the basic information about the incident ticket and click Submit.
If no shift is available for the owner, create a schedule in Overview.Figure 2 Creating an incident service ticket
NOTE:
The incident levels are defined as follows:
P1: Core service functions are unavailable, affecting all customers.
P2: Core service functions are affected, affecting the core services of some customers.
P3: An error is reported for non-core service functions, affecting some customer services.
P4: Non-core service functions are faulty. The service latency increases, the performance deteriorates, and user experience decrease.
P5: Non-core service exception occurs, which is customer consultation or request issue.
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.
For any further questions, feel free to contact us through the chatbot.
Chatbot