Error Codes¶
Function¶
If an error occurs during API calling, the system returns error information. This section describes the error codes contained in the error information for Cloud Eye APIs.
Example Response¶
{
"code": 400,
"element": "Bad Request",
"message": "The system received a request which cannot be recognized",
"details": {
"details": "Some content in message body is not correct",
"code": "ces.0014"
}
}
Glossary¶
Glossary | Description |
|---|---|
Cloud Eye | Cloud Eye |
Built-in metric | Each service has its own built-in metrics and dimensions. For example, an ECS (SYS.ECS) supports cpu_util. |
Metric | A metric consists of the namespace, dimension (optional), and metric name. A metric name solely does not identify any object. |
Error Code Description¶
Module | HTTP Status Code | Error Code | Error Code Description | Error Message | Measure |
|---|---|---|---|---|---|
Cloud Eye | 500 | ces.0007 | Internal service error | Internal service error. | Contact technical support. |
API | 400 | ces.0001 | The request content cannot be empty. | The content must be specified. | Specify the request content. |
400 | ces.0003 | The project ID is left blank or is incorrect. | The tenant ID is left blank or incorrect. | Add or use the correct tenant ID. | |
400 | ces.0004 | The API version is not specified. | The API version must be specified. | Specify the API version in the request URL. | |
400 | ces.0005 | The API version is incorrect. | The API version is incorrect. | Use the correct API version. | |
400 | ces.0006 | The paging address is incorrect. | The paging address is incorrect. | Use correct pagination information. | |
403 | ces.0009 | System metrics cannot be added. | Adding SYS metric is not allowed | Use correct rights to add metrics. | |
403 | ces.0010 | System metrics cannot be deleted. | Deleting SYS metric is not allowed | Use correct rights to delete metrics. | |
400 | ces.0011 | The request is invalid. | The request is invalid. | Check the request. | |
400 | ces.0013 | The URL parameter is invalid or does not exist. | The URL parameter is invalid or does not exist. | Check the URL parameter. | |
400 | ces.0014 | Some content in the message body is correct. | Some content in message body is not correct. | Check the request body parameters. | |
401 | ces.0015 | Authentication fails or valid authentication information is not provided. | Authentication fails or the authentication information is not provided. | Check whether the user name or password (or AK or SK) for obtaining the token is correct. | |
404 | ces.0016 | The requested resource does not exist. | The requested resource does not exist. | Check whether the requested resource exists. | |
403 | ces.0017 | The authentication information is incorrect or the service invoker does not have sufficient rights. | The authentication information is incorrect or the service invoker does not have sufficient rights. | Check whether the user name or password (or AK or SK) or the user rights for obtaining the token are correct. | |
Cassandra | 500 | ces.0008 | Database error | Database error. | Contact technical support. |
Kafka | 500 | ces.0012 | The message queue is abnormal or is not ready. | The message queue is abnormal or is not ready. | Contact technical support. |
Zookeeper | 500 | ces.0021 | Internal locking error | Internal locking error | Contact technical support. |
Blueflood | 500 | ces.0019 | The metric processing engine is abnormal. | The metric processing engine is abnormal. | Contact technical support. |
Alarm | 400 | ces.0002 | The alarm ID cannot be left blank. | The alarm ID must be specified. | Specify the alarm ID. |
403 | ces.0018 | The number of alarm rules created exceeds the quota. | The number of alarms exceeds the quota | Apply for a higher alarm quota. | |
400 | ces.0028 | The metric and notification type do not match when an alarm rule is created. | The metric does not support the alarm action type. | Modify the metric or notification type according to the parameter description to make them match. |