- 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
Copied.
Basic Concepts
Topology
A topology graphically displays call and dependency relationships between applications. It is composed of circles, lines with arrows, and resources. Each circle represents a service, and each section in the circle represents an instance. The fraction in each circle indicates number of active instance/total number of instances. The values below the fraction separately indicate the service latency, number of calls, and number of errors. Each line with an arrow represents a call relationship. Thicker lines indicate more calls. The values next to each line respectively indicate the throughput and overall latency. Throughput is the number of calls in a specified time range. Application Performance Index (Apdex) is used to quantify user satisfaction with application performance. Different colors indicate different Apdex value ranges, helping you quickly detect and locate performance problems.
Transaction
A transaction is usually an HTTP request (complete process: user request > web server > database > web server > user request). In real life, a transaction is a one-time task. A user completes a task by using an application. In the example of an e-commerce application, querying a product is a transaction, and making a payment is also a transaction.
Tracing
APM traces and records service calls, and visually presents the execution tracks and statuses of service requests in distributed systems, so that you can quickly locate performance bottlenecks and faults.
Application
An application is a group of the same or similar services categorized based on service requirements. You can put services that fulfill the same function into one application for performance management. For example, you can put accounts, products, and payment services into the Mall application.
Apdex
Apdex is an open standard developed by the Apdex alliance. It defines a standard method to measure application performance. The Apdex standard converts the application response time into user satisfaction with application performance in the range of 0 to 1.
- Apdex principle
Apdex defines the optimal threshold (T) for the application response time. T is determined by the performance evaluation personnel based on performance expectations. Based on the actual response time and T, user experience can be categorized as follows:
Satisfied: indicates that the actual response time is shorter than or equal to T. For example, if T is 1.5s and the actual response time is 1s, user experience is satisfied.
Tolerating: indicates that the actual response time is greater than T, but shorter than or equal to 4T. For example, if T is 1s, the tolerable upper threshold for the response time is 4s.
Frustrated: indicates that the actual response time is greater than 4T.
- Apdex calculation method
In APM, the Apdex threshold is the value configured in Setting Apdex Thresholds. The application response latency is the service latency. The Apdex value ranges from 0 to 1 and is calculated as follows:
Apdex = (Number of satisfied samples + Number of tolerating samples x 0.5)/Total number of samples
Apdex indicates application performance status, that is, user satisfaction with application performance. Different colors indicate different Apdex ranges, as shown in Table 1.
Apdex |
Color |
Description |
---|---|---|
0.75 ≤ Apdex ≤ 1 |
Green |
Fast response; good user experience |
0.3 ≤ Apdex < 0.75 |
Yellow |
Slow response; fair user experience |
0 ≤ Apdex < 0.3 |
Red |
Very slow response; poor user experience |
- |
Black |
No application, instance, or transaction is invoked. |
- Configuring an Apdex threshold
You can configure an Apdex threshold according to Setting Apdex Thresholds.
TP99 Latency
TP99 latency is the minimum time meeting requirements of 99% requests. In APM, latency refers to TP99 latency.
Example: Assume that there are 100 requests, and the time consumed by the requests is 1s, 2s, 3s, 4s...98s, 99s, and 100s. To meet the requirements of 99% requests, at least 99s is required. Therefore, TP99 latency is 99s.
Calculation: Sort all requests by the consumed time in ascending order. TP99 latency = Time consumed by the Nth request. N is the rounded value of 99% x Total number of requests.
Overall Latency/Service Latency
Latency refers to the period from initiating a request to getting a response. In APM, the overall latency refers to the total time consumed by a request, and the service latency refers to the time consumed by a service. The relationship is as follows: Service latency = Overall latency – Latency for calling other services. For example, assume that service A calls service B, and service B calls service C, as shown in the following figure:
- Service A: Overall latency = Ta; Service latency = Ta – Tb1 – Tb2 – Tc
- Service B: Overall latency = Tb1 + Tb2 + Tc; Service latency = Tb1 + Tb2
- Service C: Overall latency = Tc; Service latency =Tc
Probes
Probes use the bytecode enhancement technology to track calls and generate data. The data will be collected by the ICAgent and then displayed on the UI. If the memory detection mechanism is enabled and the instance memory is too large, probes enter the hibernation state, that is, stop collecting data. How Does APM Collect Probe Data?
Mesh
The Istio mesh obtains input and output application program data in non-intrusive mode. Then, the ICAgent and Cloud Container Engine (CCE) Istio mixer obtain and process the mesh data, and report it to APM. You can enable the Istio to collect mesh data. How Does APM Collect Mesh Data?
ICAgent
ICAgent is a collection agent of APM. It runs on the server where applications are deployed to collect the data obtained by probes in real time. For details about the data collection and purposes, see APM Service Agreement. Installing the ICAgent is prerequisite for using APM.
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