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/
Faults/
Incident Management/
Handling an Incident/
Full-Link Fault Diagnosis
Copied.
Full-Link Fault Diagnosis
Scenarios
After an incident is created, you can use the full-link fault diagnosis function to quickly locate the root cause of the fault. We provide the relationship topology of the application layer, component layer, and resource layer for customer applications, implement exception coloring based on resource and application alarms, and provide the capabilities of viewing core resource metrics and diagnosing instances.
Prerequisites
- You have performed the operations described in Creating an Application, Manually Associating Resources with a Group, and Editing an Application Topology on CloudCMDB.
- CES has been connected. You can configure CES monitoring by referring to Integration Management.
- An incident ticket has been created.
- To display workload and POD information in a CCE cluster, you need to add label to workloads in CCE. (Only one CCE cluster resource can be added to each group. Otherwise, workload information is not displayed.)
Figure 1 Configuring CCE workload label
Procedure
- Log in to COC.
- In the navigation pane, choose Fault Management > Incidents, click the All Incident Tickets tab, click an incident name to go to the Incident Details page, and click the Application Diagnostics tab.
- Select a fault time range to color the alarms generated in this time range. You can enter the end time in the time box. The start time is one hour earlier than the end time. The time axis can be automatically refreshed. After Auto Refresh is selected, the end time is automatically refreshed to the latest time based on the refresh frequency.
Figure 2 Selecting fault time range
- By default, all sub-applications of the current application are displayed on the application topology screen.
Figure 3 Application topology (application layer)
- Click a sub-application in the topology to view the component layer. All components of the sub-application are displayed. You can switch to other sub-applications on the top to view their components.
Figure 4 Application topology (component layer)
- Click a component to view the resource layer. All resources under the component are displayed, and metrics of core cloud services are displayed. If APM is associated in application management, you can also view link-related metrics.
Figure 5 Application topology (resource layer)
- Click the Alarm tab to view application alarms. The list displays the alarms generated within the time range. After a topology object is selected on the left, the alarm information of the selected object is automatically filtered out.
Figure 6 Alarm list
- Click the Change tab to view application changes. The list displays the changes within the time range.
Figure 7 Changes
- Click the Diag tab and click Create Diag to diagnose DCS, RDS, and DMS resources of an application. After a topology object is selected on the left, the diagnosis information of the selected object is automatically filtered out.
Figure 8 Creating a diagnosis task
- After the diagnosis is complete, click View Details in the diagnosis result list to view the diagnosis report.
Figure 9 Diagnosis report
Parent topic: Handling an Incident
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