Updating Scheduled Check Settings for Intelligent O&M
Function
CSS provides intelligent O&M to check potential risks in clusters on a daily basis. This API is used to configure scheduled checks for intelligent O&M.
Calling Method
For details, see Calling APIs.
URI
POST /v1.0/{project_id}/clusters/{cluster_id}/ai-ops/setting
| Parameter | Mandatory | Type | Description |
|---|---|---|---|
| project_id | Yes | String | Definition: Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name. Constraints: N/A Value range: Project ID of the account. Default value: N/A |
| cluster_id | Yes | String | Definition: ID of the cluster to be queried. For details about how to obtain the cluster ID, see Obtaining the Cluster ID. Constraints: N/A Value range: Cluster ID. Default value: N/A |
Request Parameters
| Parameter | Mandatory | Type | Description |
|---|---|---|---|
| check_type | Yes | String | Definition: Check type Value range:
Default value: N/A |
| check_items | No | Array of strings | Definition: Select a subset of all check items, and enter the check item list. Value range: N/A Default value: N/A |
| period | Yes | String | Definition: Intelligent O&M automatic check time, in the form of time followed by time zone, for example, 00:00 GMT+08:00. Value range: N/A Default value: N/A |
Response Parameters
Status code: 200
Request succeeded.
None
Example Requests
None
Example Responses
None
Status Codes
| Status Code | Description |
|---|---|
| 200 | Request succeeded. |
| 400 | Invalid request. Modify the request directly and do not attempt to retry it. |
| 409 | The request cannot be processed due to a conflict. This status code indicates that the resource that the client attempts to create already exists, or the request failed to be processed because of the update of the conflict request. |
| 412 | The server does not meet one of the preconditions that the client puts on the request. |
Error Codes
See Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.