- 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
- Package Pricing Details of Probe Product - Professional Edition
- Package Pricing Details of Probe Product - Enterprise Edition
- Package Pricing Details of Probe Product - Platinum Edition
- Package Pricing Details of Probe Product - Basic Edition
- Pay-per-Use Pricing Details of Different Probe Product Editions
- Billing Rules for Pay-per-Use Resources
Show all
Copied.
Pricing Details
APM supports both pay-per-use and package billing. When you subscribe to APM, the package - basic edition is used by default. To use other editions, purchase them as required.
Currently, APM supports Java and PHP applications.
Package Pricing Details of Probe Product - Professional Edition
Region |
Probes |
1 Month |
1 Year |
Currency |
---|---|---|---|---|
CN North-Beijing4 CN East-Shanghai1 |
10 |
136 |
1,357 |
USD |
20 |
271 |
2,715 |
USD |
|
50 |
679 |
6,787 |
USD |
|
100 |
1,357 |
13,574 |
USD |
|
200 |
2,443 |
24,433 |
USD |
|
500 |
5,769 |
57,689 |
USD |
|
1,000 |
10,859 |
108,592 |
USD |
|
2,000 |
19,004 |
190,036 |
USD |
|
CN-Hong Kong AP-Singapore AP-Bangkok LA-Santiago AF-Johannesburg |
10 |
220 |
2,205 |
USD |
20 |
441 |
4,411 |
USD |
|
50 |
1,102 |
11,029 |
USD |
|
100 |
2,205 |
22,058 |
USD |
|
200 |
3,970 |
39,705 |
USD |
|
500 |
9,375 |
93,750 |
USD |
|
1,000 |
17,647 |
176,470 |
USD |
|
2,000 |
30,882 |
308,823 |
USD |
Package Pricing Details of Probe Product - Enterprise Edition
Region |
Probes |
1 Month |
1 Year |
Currency |
---|---|---|---|---|
CN North-Beijing4 CN East-Shanghai1 |
10 |
271 |
2,715 |
USD |
20 |
543 |
5,430 |
USD |
|
50 |
1,357 |
13,574 |
USD |
|
100 |
2,443 |
24,433 |
USD |
|
200 |
4,887 |
48,866 |
USD |
|
500 |
10,859 |
108,592 |
USD |
|
1,000 |
19,004 |
190,036 |
USD |
|
2,000 |
38,007 |
380,071 |
USD |
|
CN-Hong Kong AP-Singapore AP-Bangkok LA-Santiago AF-Johannesburg |
10 |
441 |
4,411 |
USD |
20 |
882 |
8,823 |
USD |
|
50 |
2,205 |
22,058 |
USD |
|
100 |
3,970 |
39,705 |
USD |
|
200 |
7,941 |
79,411 |
USD |
|
500 |
17,647 |
176,470 |
USD |
|
1,000 |
30,882 |
308,823 |
USD |
|
2,000 |
61,764 |
617,647 |
USD |
Package Pricing Details of Probe Product - Platinum Edition
Region |
Probes |
1 Month |
1 Year |
Currency |
---|---|---|---|---|
CN North-Beijing4 CN East-Shanghai1 |
200 |
19,004 |
190,036 |
USD |
500 |
38,007 |
380,071 |
USD |
|
1,000 |
80,765 |
807,651 |
USD |
|
2,000 |
133,025 |
1,330,249 |
USD |
|
CN-Hong Kong AP-Singapore AP-Bangkok LA-Santiago AF-Johannesburg |
200 |
30,882 |
308,823 |
USD |
500 |
61,764 |
617,647 |
USD |
|
1,000 |
131,250 |
1,312,500 |
USD |
|
2,000 |
216,176 |
2,161,764 |
USD |
Package Pricing Details of Probe Product - Basic Edition
Region |
Probes |
1 Month |
1 Year |
Currency |
---|---|---|---|---|
CN North-Beijing4 CN East-Shanghai1 CN-Hong Kong AP-Singapore AP-Bangkok LA-Santiago AF-Johannesburg |
Unlimited (Data collection lasts for one hour each time and then automatically stops. Max. data collection times: 50.) |
0 |
0 |
USD |
Pay-per-Use Pricing Details of Different Probe Product Editions
Region |
Billing Mode |
Basic |
Professional |
Enterprise |
Platinum |
Pricing Basis (USD) |
---|---|---|---|---|---|---|
CN North-Beijing4 CN East-Shanghai1 CN-Hong Kong AP-Singapore AP-Bangkok LA-Santiago AF-Johannesburg |
Pay-per-use |
0 |
0.044 |
0.088 |
0.308 |
Price per instance-hour |
ME-Abu Dhabi-OP5 |
Pay-per-use |
0 |
0.0485 |
0.09700000000000002 |
0.3395 |
Price per instance-hour |
- Probes will be billed by hour (rounded up to the nearest one hour).
- A professional-edition probe is one billing unit. An enterprise-edition probe is billed by two billing units. A platinum-edition probe is billed by seven billing units. A probe billing unit refers to the basic billing unit of probes during pay-per-use or package billing. Probes of different editions can be converted into certain number of probe billing units for billing.
- Packages are purchased with one-off payments and take effect immediately upon your payment. You cannot specify a later date for the packages to take effect.
- Multiple packages can be used together.
- During the validity period of a package, if you use more resources than those included in the package, you will be billed on a pay-per-use basis for the excess resources used.
- Packages need to be renewed before they expire. Otherwise, resources will be billed on a pay-per-use basis.
- Package unsubscription is not supported. After a resource package expires, you can continue using APM and your data is still secure.
Billing Rules for Pay-per-Use Resources
- Standard pricing: You pay only for what you use, based on the unit price of the resources you use and how long or often you use them. The cost is accurate to two decimal places.
- Tiered pricing: Pay less by using longer or more. The cost is accurate to two decimal places.
- For pay-per-use billing, decimal numerals on the price calculator are rounded off and are accurate to two decimal places. If the fee is less than $0.01 USD (after rounding off), $0.01 USD will be displayed.
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