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
Show all
Clearing Alarms
Updated on 2025-03-17 GMT+08:00
- Log in to COC.
- In the navigation pane on the left, choose Fault Management > Alarms. On the displayed page, click Aggregated alarm > Unhandled Alarms tabs.
- Select the alarms to be deleted and click Clear in the Operation column or above the alarm list.
- Set Service interrupted. If you select No, go to step 5. If you select Yes, you must set Fault occurrence time and Fault recovery time. The service interruption time is included in the SLO interruption record of the corresponding application.
Figure 1 Clearing Alarms - Service Interruption
NOTE:
To generate an SLO interruption record, you need to set the corresponding SLA rule and SLO rule, and the alarm has the corresponding SLA record.
- Enter the remarks and click OK to clear the alarms.
NOTE:
The remarks can contain at most 100 characters, including letters, digits, and special characters.
Parent topic: Alarms
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.