Tencent Cloud Observability Platform
- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Application Performance Management
- Pay-as-you-go (Postpaid)
- Packages (Prepaid)
- Mobile App Performance Monitoring
- Real User Monitoring
- Cloud Automated Testing
- Prometheus Monitoring
- Pay-as-You-Go (Postpaid)
- Quick Start
- EventBridge
- Cloud Product Monitoring
- Tencent Cloud Service Metrics
- Microservice
- Networking
- TencentDB
- TencentDB for Redis Monitoring Metrics
- CPM
- CDN And EdgeOne
- Operation Guide
- Cloud Monitoring Overview
- Monitoring View
- CM Connection to Grafana
- Troubleshooting
- Application Performance Management
- Access Guide
- Accessing Go Application
- Accessing Java Application
- Accessing Python Application
- Accessing Node.js Application
- Accessing PHP Application
- Accessing .NET Application
- Operation Guide
- Resource Management
- Application Monitoring
- Application Diagnosis
- Database Call Monitoring
- Access Management
- Alarm Service
- System Configuration
- Associate Logs
- Inject TraceID Into Logs
- Practical Tutorial
- Parameter Information
- APM Data Protocol Standard
- Mobile App Performance Monitoring
- Access Guide
- Android Use Cases
- iOS Use Cases
- Tencent Cloud Real User Monitoring
- Operation Guide
- Application Management
- Access Management
- Resource Tag
- Connection Guide
- Web Use Cases
- Cloud Automated Testing
- Operation Guide
- Creating Test Task
- Testing Statistics
- Access Management
- References
- Testing Nodes
- FAQs
- Performance Testing Service
- Operation Guide
- Performance Testing in Script Mode
- Script Examples
- HTTP-based Performance Testing
- Performance Testing in JMeter Mode
- Project Management
- Scenario Management
- Advanced Configuration
- Export Stress Test Indicators
- Traffic Recording
- Performance Testing Report
- Access Control
- Alarm Management
- Tag Management
- Practice Tutorial
- JavaScript API List
- pts/http
- Response
- pts/dataset
- pts/grpc
- pts/jsonpath
- pts/redis
- pts/url
- URL
- pts/util
- pts/ws
- pts/socketio
- socketio
- pts/socket
- Prometheus Monitoring
- Product Introduction
- Access Guide
- EMR Integration
- Java Application Integration
- Exporter Integration
- Operation Guide
- Instance
- Recording Rule
- Alerting Rule
- Access Control
- TKE Metrics
- Practical Tutorial
- Terraform
- Grafana
- Operation Guide
- Instance
- Tencent Cloud Service Integration
- Plugin Management
- Dashboard
- Operation Guide
- Configuring Dashboard
- Monitoring Charts
- Creating Chart
- Use Cases of Different Chart Types
- Alarm Management
- Console Operation Guide
- Alarm Policy
- Configuring alert trigger conditions
- Alarm Notification
- Alarm Callback
- Alarm Receiving Channels and SMS Quota
- Dynamic Threshold Alarm
- Silencing Alarm
- EventBridge
- Product Introduction
- Practical Tutorial
- Migrating Event Alarm
- FAQs
- Related Agreements
- API Documentation
- Making API Requests
- Monitoring Data Query APIs
- Alarm APIs
- Notification Template APIs
- Legacy Alert APIs
- Prometheus Service APIs
- Grafana Service APIs
- Event Center APIs
- TencentCloud Managed Service for Prometheus APIs
- Monitoring APIs
DocumentationTencent Cloud Observability PlatformPurchase GuideApplication Performance ManagementPackages (Prepaid)Introduction to Packages
Introduction to Packages
Last updated: 2025-03-25 16:20:53
Application Performance Management (APM) offers packages, which can reduce the cost in specific scenarios. You can choose to purchase them by yourself.
Billing Description
Packages are charged based on the number of probes (Agents) and usage hours. The single billing item is Agent * Hour. One Agent corresponds to one application process integrated with APM. After each application process is integrated with APM, it will consume 1 Agent * Hour per hour. For example, if 10 application processes are integrated with APM, 10 * 24 = 240 Agent * Hours will be consumed every day.
Package Pricing
Package Type | Validity Period | Specification (Number of Probes * Per Hour) | Price (USD) |
Developer - Experience Edition | One month | 3,600 | 150 USD |
Developer - Standard Edition | One month | 28,800 | 887 USD |
Enterprise - Basic Edition | One year | 273,600 | 6,022 USD |
Enterprise - Professional Edition | One year | 1,080,000 | 17,215 USD |
Flagship Edition | One year | 3,600,000 | 51,508 USD |
Purchase Notice
The business system supports two payment modes: pay-as-you-go and prepaid. Only in prepaid mode can the package offset the amount. If you change the business system from pay-as-you-go mode to prepaid mode, it will take effect the next day. After it takes effect, the package can offset the amount.
If your package limit has been used up, it will not affect data reporting. The part exceeding the package limit will be settled in pay-as-you-go mode. For more information about pay-as-you-go mode, please refer to Introduction to Pay-as-you-go.
Packages cannot be used across regions. Ensure that the region for purchasing the package is correct.
When the amount is offset by the package, the global sampling rate will be fixed at 10%, and the full sampling API will not take effect. If you need to retain all link data or customize the sampling percentage, please use the pay-as-you-go mode.
Please use up the package limit within the valid period. After the expiration date, the package will be in an expired state and can no longer offset the amount.
Supports purchasing multiple packages at the same time, and package limits can be stacked.
The package is shared by all business systems in the same region under the entire account.
Deduction Notice
If there are multiple available packages in the same region, they will be deducted in order from the nearest expiration time to the farthest. When the expiration times are the same, the one with the earlier purchase date will be deducted first.
Example:
Assume that you have purchased three packages in the same region:
Package A: Basic version for business, Effective time: 2023-10-01 00:00:00 - 2024-09-30 23:59:59.
Package B: Developer experience edition package, Effective time: 2024-09-01 00:00:00 - 2024-09-30 23:59:59.
Package C: Standard version for developers, Effective time: 2024-08-15 00:00:00 - 2024-09-15 23:59:59.
The deduction sequence of the three packages is: C > A > B.
Refund Instructions
Expiration Reminder
When the package limit is insufficient or approaching expiration, Application Performance Monitoring (APM) will send you message reminders via Short Message Service (SMS), mail, etc.
Send message reminders when the package limit remains at 30%, 15%, 5%, and 0%.
Send message reminders when the package's valid period has 7 days, 3 days, or 1 day remaining.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No