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/
FAQs/
FAQs About Fault Management/
What Is the Process of Generating an Incident?
What Is the Process of Generating an Incident?
Updated on 2025-01-14 GMT+08:00
There are three methods available: manual incident creation, converting alarms to incidents, or automatically generate an incident based on an incident forwarding rule. The detailed processes of the three operation methods are as follows.
Manually Creating an Incident
Choose Fault Management > Incidents and click Create to create an incident ticket. For details, see Creating an Incident.
Converting an Alarm to an Incident
Choose Fault Management > Incidents to create an incident ticket. For details, see section "Converting an Alarm to an Incident".
Automatically Generating Incidents Based on Forwarding Rules
To automatically generate an incident based on a forwarding rule, perform the following operations:
- Log in to COC.
- Synchronize personnel. For details, see O&M Engineer Management Overview.
- Set shift scheduling and add agents to the shift scheduling. For details, see Overview.
- Integrate with the monitoring system to automatically report alarms. For details, see Monitoring System Integration Management.
- Configure transition rules and generate incidents based on the rules. For details, see Forwarding rules.
- To receive incident notifications after an incident is generated, configure the automated notification feature. For details, see Notification Management.
Parent topic: FAQs About Fault 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.