- 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
Creating an Issue Ticket
Scenarios
Create an issue ticket on COC.
Prerequisites
You have created an application by referring to Application Management.
Procedure
- Log in to COC.
- In the navigation pane, choose Fault Management > Issues. Click Create Issue Ticket in the upper right corner.
Figure 1 Issue list
- Enter basic information about the issue and click Submit.
Figure 2 Page for creating an issue
Issue Title: Mandatory. Briefly describe the issue.
Issue Description: Mandatory. Describe the issue and its impact on the live network. Attachments can be uploaded.
Issue Source: Optional. Enter the issue source, which can be incidents, alarms, war rooms, or detection results in proactive O&M. If the issue is found during incident handling, select Incident.
Issue.table.occurTime: Optional. Enter the time when the issue occurs.
Issue Application: Mandatory. Select the application to which the issue belongs.
Issue Level: Mandatory. Select the issue level, including Critical, Major, Minor, and Prompts.
Type of Issue: Mandatory. Select the issue type.
Owner: Mandatory. After an owner is selected, the issue ticket will be transferred to the owner. Currently, Shift and Individual are supported. For details about how to set shift, see Shift Schedule Management.
NOTICE:
To receive notifications for issues, you need to configure notification rules on the Notification Management page. For details, see Notification Management.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.