- 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.
CSEProvider Cluster Monitoring
This section describes the types, names, and meanings of CSEProvider cluster metrics collected by APM.
Parameter |
Data Type |
Application Type |
Default |
Supported Start Agent Version |
Supported End Agent Version |
Description |
---|---|---|---|---|---|---|
Blocklist Configuration |
obj_array |
JAVA |
- |
2.0.0 |
- |
URLs in the blacklist will not be collected. There are four modes: "startwith", "endwith", "include", and "regex". |
Max. Status Code Length |
integer |
JAVA |
0 |
2.0.0 |
- |
The system parses the body content within the specified length and obtains the corresponding service status code. |
Key for Status Code Parsing |
array |
JAVA |
- |
2.0.0 |
- |
Key based on which the corresponding body content is to be obtained and reported as the service status code |
Normal Status Code |
array |
JAVA |
- |
2.0.0 |
- |
If the obtained status code is not within the range, the request is regarded as an error trace. |
Slow Request Threshold |
integer |
JAVA |
800 |
2.0.0 |
- |
Slow request threshold. If the threshold is crossed, a URL will be regarded as a slow URL. The system will automatically increase the sampling ratio for it. |
Slow URL Threshold |
obj_array |
JAVA |
- |
2.0.0 |
- |
Slow request threshold. If this threshold is crossed, the URL is defined as a slow URL. In that case, the system automatically increases the sampling ratio for it. There are four sampling policies: 1. Full sampling; 2. Percentage sampling; 3. Fixed-quantity sampling per minute; 4. Automatic sampling. |
Key for Header Value Interception |
array |
JAVA |
- |
2.0.0 |
- |
Key based on which header value content is to be intercepted |
Category |
Metric |
Name |
Description |
Unit |
Data Type |
Default Aggregation Mode |
---|---|---|---|---|---|---|
CSEProvider cluster monitoring (cluster: APM counts call statistics based on the ID of the caller's cluster.) |
clusterId |
Cluster ID |
Cluster ID of the caller |
- |
ENUM |
LAST |
errorCount |
Errors |
Number of times that the cluster fails to be called |
- |
INT |
SUM |
|
invokeCount |
Calls |
Number of cluster calls |
- |
INT |
SUM |
|
maxTime |
Max. RT |
Maximum response time for calling the cluster |
ms |
INT |
MAX |
|
totalTime |
Total RT |
Total response time for calling the cluster |
ms |
INT |
SUM |
|
CSEProvider call details (detail: APM counts call statistics by URL.) |
qualifiedName |
Call URL |
Called URL of CSEProvider |
- |
ENUM |
LAST |
method |
HTTP Method |
HTTP method of the called CSEProvider URL |
- |
ENUM |
LAST |
|
concurrentMax |
Max. Concurrency |
Maximum concurrency of the CSEProvider URL |
- |
INT |
MAX |
|
errorCount |
Errors |
Number of errors occur when the CSEProvider URL is called |
- |
INT |
SUM |
|
invokeCount |
Calls |
Number of times that the CSEProvider URL is called |
- |
INT |
SUM |
|
lastError |
Error Message |
Call error details |
- |
STRING |
LAST |
|
maxTime |
Max. RT |
Maximum response time for calling the CSEProvider URL |
ms |
INT |
MAX |
|
totalTime |
Total RT |
Total response time for calling the CSEProvider URL |
ms |
INT |
SUM |
|
range1 |
0–10 ms |
Number of requests with 0–10 ms response time |
- |
INT |
SUM |
|
range2 |
10–100 ms |
Number of requests with 10–100 ms response time |
- |
INT |
SUM |
|
range3 |
100–500 ms |
Number of requests with 100–500 ms response time |
- |
INT |
SUM |
|
range4 |
500–1000 ms |
Number of requests with 500–1000 ms response time |
- |
INT |
SUM |
|
range5 |
1–10s |
Number of requests with 1–10s response time |
- |
INT |
SUM |
|
range6 |
> 10s |
Number of requests with response time longer than 10s |
- |
INT |
SUM |
|
CSEProvider summary (total: summary of all URL statistics) |
errorCount |
Errors |
Total number of CSEProvider call errors |
- |
INT |
SUM |
invokeCount |
Calls |
Total number of CSEProvider calls |
- |
INT |
SUM |
|
totalTime |
Total RT |
Total response time of calling CSEProvider |
ms |
INT |
SUM |
|
Status code monitoring (statuscode: APM counts URL call statistics based on the status code returned.) |
code |
Status Code |
HTTP status code |
- |
ENUM |
LAST |
count |
Count |
Number of times that the status code has occurred |
- |
INT |
SUM |
|
url |
Sample URL |
Sample URL which returns the status code |
- |
STRING |
LAST |
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