- 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
Verifying the Incident Handling Result
Function
This API is used to verify the incident ticket.
URI
POST /v1/external/incident/handle
Remarks: The URIs of operations such as handling, submitting solutions, and verifying solutions are the same.
Request Parameters
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
incident_num |
Yes |
String |
Incident ticket ID Minimum length: 0 character Maximum length: 255 characters |
operator |
Yes |
String |
Operator ID Minimum length: 0 character Maximum length: 255 characters |
operate_key |
Yes |
String |
Operation type. The value is confirm. Minimum length: 0 character Maximum length: 255 characters Fixed value |
parameter |
Yes |
Map<String,Object> |
Input parameters |
parameter.virtual_confirm_result |
Yes |
Boolean |
Verification result. The value can be true (default) or false. |
parameter.virtual_confirm_comment |
Yes |
String |
Verification description. The value contains a maximum of 300 characters. |
Response Parameters
Status code: 200
Parameter |
Type |
Description |
---|---|---|
provider_code |
String |
Service ID. Default value: 049 Minimum length: 3 characters Maximum length: 100,000,000 characters |
error_code |
String |
Request response code. The value ranges from 0000 to 9999. The value is 0 in normal cases. Default value: GOM.00000000 request success Minimum length: 1 character Maximum length: 100,000,000 characters |
error_msg |
String |
Request response description. Minimum length: 0 character Maximum length: 100,000,000 characters |
Status code: 400
Parameter |
Type |
Description |
---|---|---|
provider_code |
String |
Service ID. Default value: 049 Minimum length: 3 characters Maximum length: 100,000,000 characters |
error_code |
String |
Request response code. The value ranges from 0000 to 9999. The value is 0 in normal cases. Default value: GOM.00000000 Minimum length: 1 character Maximum length: 100,000,000 characters |
error_msg |
String |
Request response description. Minimum length: 0 character Maximum length: 100,000,000 characters |
Request Example
GET https://IP:PORT/v1/external/incident/handle Request Headers: Content-Type: application/json X-Auth-Token: MI*******ghkgB { "incident_num":"IM202403221515060171753781", "operator":"7da46971b7e24eed90cf777cc2ff8b91", "operate_key":"confirm", "parameter":{ "virtual_confirm_result": false, "virtual_confirm_comment": "13" } }
Response Example
{ "provider_code": "049", "error_code": "GOM.00000000", "error_msg": null, "data": null }
Status Code
Status Code |
Description |
---|---|
200 |
response |
400 |
Error response |
Error code
None
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.