- What's New
-
Service Overview(2.0)
- What Is APM
- Functions
- Application Scenarios
- Basic Concepts
- Edition Differences
- Permissions Management
-
Metric Overview
- Exception
- Basic Monitoring
-
Databases
- C3P0 Connection Pool Monitoring
- Cassandra Monitoring
- ClickHouse Database
- DBCP Connection Pool Monitoring
- Druid Connection Pool Monitoring
- EsRestClient Monitoring
- GaussDB Database
- HBase Monitoring
- Hikari Connection Pool Monitoring
- Jetcd Monitoring
- MongoDB Monitoring
- MySQL Database
- ObsClient Monitoring
- Oracle Database
- PostgreSQL Database
- URLs
- External Calls
- Cache
- Agent Monitoring
- Tomcat Monitoring
- Message Queues
- RPC
- IoT
- Communication Protocol
- Privacy and Sensitive Information Protection Statement
- Data Collection
- Usage Restrictions
- Billing
- JavaAgent Updates
- Billing(2.0)
- Getting Started(2.0)
-
User Guide(2.0)
- Before You Start
- Application List
- CMDB Management
-
Application Metric Monitoring
- Overview
- Application Monitoring Details
-
Application Monitoring Configuration
- Configuration Details
- Configuring the MySQL Monitoring Item
- Configuring the HttpClient Monitoring Item
- Configuring the URL Monitoring Item
- Configuring the JavaMethod Monitoring Item
- Configuring the Druid Monitoring Item
- Configuring the ApacheHttpAsyncClient Monitoring Item
- Configuring the Redis Monitoring Item
- Configuring the Jedis Monitoring Item
- Configuring the HBase Monitoring Item
- Configuring the ApacheHttpClient Monitoring Item
- Configuring the Tomcat Monitoring Item
- Configuring the EsRestClient Monitoring Item
- Configuring the WebSocket Monitoring Item
- Configuring the KafkaProducer Monitoring Item
- Configuring the Hikari Monitoring Item
- Configuring the Exception Monitoring Item
- Configuring the Thread Monitoring Item
- Configuring the GC Monitoring Item
- Configuring the JVMInfo Monitoring Item
- Configuring the JVMMonitor Monitoring Item
- Configuring ProbeInfo Monitoring Item
- Monitoring Item Views
- Instance
- Collection Status
- Component Settings
- Tracing
- Application Topology
- URL Tracing
- Resource Tag Management
- Managing Tags
- Alarm Management
- AgentAgent Management
- Configuration Management
- System Management
- Permissions Management
- Change History
-
API Reference(2.0)
- Before You Start
- API Overview
- Calling APIs
- Examples
-
APIs
-
APM
- Querying the application list.
- Querying the Master Address
- Obtaining the AK/SK
- Searching for Components, Environments, and Agents in a Region
- Saving a Monitoring Item
- Querying the Monitoring Item List
- Querying All Agents of an Application
- Enabling or Disabling Collection for an Instance
- Deleting an Agent
- REGION
- CMDB
-
VIEW
- Querying Monitoring Item Configurations
- Querying the Trace Topology
- Querying Event Details
- Querying Span Data
- Obtaining All Data of a Trace
- Obtaining the Trend Graph
- Obtaining Summary Table Data
- Obtaining the Raw Data Table
- Obtaining Raw Data Details
- Obtaining the Instance Information
- Obtaining the Monitoring Item Information
- Obtaining the Details About a Monitoring Item
- AKSK
- ALARM
- TOPOLOGY
- TRANSACTION
- TRACING
-
APM
- Permissions Policies and Supported Actions
- Appendix
- Change History
- Best Practices(2.0)
- FAQs(2.0)
- Service Overview(1.0)
- Getting Started(1.0)
- Best Practices(1.0)
- User Guide
- API Reference
- SDK Reference
-
FAQs
- General FAQs
- Consultation FAQs
-
Usage FAQs
- How Do I Obtain the AK/SK and Project ID?
- How Do I Obtain the AK/SK by Creating an Agency?
- What Can I Do If No Data Is Found or the Data Is Abnormal?
- How Do I Connect APM to Non-Web Programs?
- How Are Tracing Time Lines Drawn?
- How Does APM Collect Probe Data?
- How Does APM Collect Mesh Data?
- How Do I Calculate the Number of Used Instances?
- How Do I Connect the JBoss Server in Standalone Mode to APM?
- What Can I Do If I Cannot Search for Logs Based on Trace IDs?
- How Do I Deploy APM Probes in CCE Containers?
- What Can I Do If the SSH Tunnel Process Is Abnormal?
- How Can I Do If No Topology or Data Is Displayed After the ICAgent and Java Probes Are Installed?
- Why Are Tomcat Thread Metrics Not Displayed on the JVM Monitoring Page?
- Why Is the Allocated Memory Greater Than the Preset Maximum Memory on the JVM Monitoring Page?
- How Do I Determine Whether an ICAgent Has Been Bound in CCE?
-
More Documents
- User Guide (ME-Abu Dhabi Region)
- API Reference (ME-Abu Dhabi Region)
-
User Guide (2.0) (Kuala Lumpur Region)
-
Service Overview
- What Is APM
- Functions
- Application Scenarios
- Basic Concepts
- Edition Differences
- Permissions Management
-
Metric Overview
- Metric Overview
- Exception
- Basic Monitoring
-
Databases
- C3P0 Connection Pool Monitoring
- Cassandra Monitoring
- ClickHouse Database
- DBCP Connection Pool Monitoring
- Druid Connection Pool Monitoring
- EsRestClient Monitoring
- GaussDB Database
- HBase Monitoring
- Hikari Connection Pool Monitoring
- Jetcd Monitoring
- MongoDB Monitoring
- MySQL Database
- ObsClient Monitoring
- Oracle Database
- PostgreSQL Database
- URLs
- External Calls
- Cache
- Agent Monitoring
- Tomcat Monitoring
- Message Queues
- RPC
- IoT
- Communication Protocol
- Privacy and Sensitive Information Protection Statement
- Data Collection
- Usage Restrictions
- Getting Started
-
User Guide
- Before You Start
- Application List
- CMDB Management
-
Application Metric Monitoring
- Overview
- Application Monitoring Details
-
Application Monitoring Configuration
- Configuration Details
- Configuring the MySQL Monitoring Item
- Configuring the HttpClient Monitoring Item
- Configuring the URL Monitoring Item
- Configuring the JavaMethod Monitoring Item
- Configuring the Druid Monitoring Item
- Configuring the ApacheHttpAsyncClient Monitoring Item
- Configuring the Redis Monitoring Item
- Configuring the Jedis Monitoring Item
- Configuring the HBase Monitoring Item
- Configuring the ApacheHttpClient Monitoring Item
- Configuring the Tomcat Monitoring Item
- Configuring the EsRestClient Monitoring Item
- Configuring the WebSocket Monitoring Item
- Configuring the KafkaProducer Monitoring Item
- Configuring the Hikari Monitoring Item
- Configuring the Exception Monitoring Item
- Configuring the Thread Monitoring Item
- Configuring the GC Monitoring Item
- Configuring the JVMInfo Monitoring Item
- Configuring the JVMMonitor Monitoring Item
- Configuring ProbeInfo Monitoring Item
- Monitoring Item Views
- Tracing
- Application Topology
- URL Tracing
- Resource Tag Management
- Managing Tags
- Alarm Management
- Agent Management
- Configuration Management
- System Management
- Permissions Management
- FAQs
- Change History
-
Service Overview
- General Reference
Show all
Copied.
Status Code
Table 1 lists the status codes.
Status Code |
Message |
Description |
---|---|---|
100 |
Continue |
The server has received the initial part of the request and the client should continue to send the remaining part. This code is issued on a provisional basis while request processing continues. It alerts the client to wait for a final response. |
101 |
Switching Protocols |
The protocol should be switched. The target protocol must be more advanced than the source protocol. For example, the current HTTP protocol is switched to a later version of HTTP. |
200 |
OK |
The server has successfully processed the request. |
201 |
Created |
The request has been fulfilled, resulting in the creation of a new resource. |
202 |
Accepted |
The request has been accepted for processing, but the processing has not been completed. |
203 |
Non-Authoritative Information |
The server successfully processed the request, but is returning information that may be from another source. |
204 |
No Content |
The server has successfully processed the request, but does not return any content. The status code is returned in response to an HTTP OPTIONS request. |
205 |
Reset Content |
The server has successfully processed the request, but does not return any content. This response requires that the requester reset the content. |
206 |
Partial Content |
The server has successfully processed a part of the GET request. |
300 |
Multiple Choices |
There are multiple options for the requested resource. For example, this code could be used to present a list of resource characteristics and addresses from which the client such as a browser may choose. |
301 |
Moved Permanently |
This and all future requests should be permanently directed to the given URI indicated in this response. |
302 |
Found |
The requested resource was temporarily moved. |
303 |
See Other |
The response to the request can be found under another URI using a GET or POST method. |
304 |
Not Modified |
The requested resource has not been modified. In such case, there is no need to retransmit the resource since the client still has a previously-downloaded copy. |
305 |
Use Proxy |
The requested resource is available only through a proxy. |
306 |
Unused |
This HTTP status code is no longer used. |
400 |
Bad Request |
The request is invalid. The client should modify the request instead of re-initiating it. |
401 |
Unauthorized |
The authorization information provided by the client is incorrect or invalid. |
402 |
Payment Required |
This status code is reserved for future use. |
403 |
Forbidden |
The server has received the request and understood it, but the server is refusing to respond to it. The client should modify the request instead of re-initiating it. |
404 |
Not Found |
The requested resource could not be found. The client should modify the request instead of re-initiating it. |
405 |
Method Not Allowed |
A request method is not supported for the requested resource. The client should modify the request instead of re-initiating it. |
406 |
Not Acceptable |
The server could not fulfill the request according to the content characteristics of the request. |
407 |
Proxy Authentication Required |
This code is similar to 401, but indicates that the client must first authenticate itself with the proxy. |
408 |
Request Time-out |
The server timed out waiting for the request. The client may re-initiate the request without modifications at any later time. |
409 |
Conflict |
The request could not be processed due to a conflict in the request, such as an edit conflict between multiple simultaneous updates or the resource that the client attempts to create exists. |
410 |
Gone |
The requested resource has been deleted permanently and will not be available again. |
411 |
Length Required |
The server refused to process the request because the request does not specify the length of its content. |
412 |
Precondition Failed |
The server does not meet one of the preconditions that the requester puts on the request. |
413 |
Request Entity Too Large |
The server refuses to process a request because the request is too large. The server may disable the connection to prevent the client from sending requests consecutively. If the server temporarily cannot process the request, the response will contain a Retry-After header field. |
414 |
Request-URI Too Large |
The URI provided was too long for the server to process. |
415 |
Unsupported Media Type |
The server does not support the media type in the request. |
416 |
Requested range not satisfiable |
The requested range is invalid. |
417 |
Expectation Failed |
The server fails to meet the requirements of the Expect request-header field. |
422 |
Unprocessable Entity |
The request was well-formed but was unable to be followed due to semantic errors. |
429 |
Too Many Requests |
The client sends excessive requests to the server within a given time (exceeding the limit on the access frequency of the client), or the server receives excessive requests within a given time (beyond its processing capability). In this case, the client should repeat requests after the time specified in the Retry-After header of the response expires. |
500 |
Internal Server Error |
The server is able to receive the request but unable to understand the request. |
501 |
Not Implemented |
The server does not support the requested function. |
502 |
Bad Gateway |
The server was acting as a gateway or proxy and received an invalid request from a remote server. |
503 |
Service Unavailable |
The requested service is invalid. The client should modify the request instead of re-initiating it. |
504 |
Server Timeout |
The request cannot be fulfilled within a given time. This status code is returned to the client only when the timeout parameter is specified in the request. |
505 |
HTTP Version not supported |
The server does not support the HTTP protocol version used in the request. |
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.
For any further questions, feel free to contact us through the chatbot.
Chatbot