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 GuidePrometheus MonitoringManaged Collector Billing Introduction
Managed Collector Billing Introduction
Last updated: 2024-08-26 14:35:00
Note:
Based on use cases, integration Tencent Kubernetes Engine (TKE) and integration center can be differentiated:
Integration TKE: Collector resources can be free/discounted.
Simultaneously collect containers free basic metrics and chargeable container metrics. The free collector resources are calculated based on the proportion of container free basic metrics data.
Calculation method: Free resource amount = Total collector resources used by integration containers × (Container free basic metrics data / Total container metrics data)
If only containers free basic metrics is collected, fees for collector resources used by integration TKE will not be charged.
Integration center: Charges are based on collector resources used by the integration type.
Billing Mode Description
Billing mode | Payment Mode |
Pay-as-you-go (postpaid) | On-demand use. Fees will be charged based on your actual resource usage upon settlement. |
Collector Pricing
Calculation Formula
Total cost = CPU usage (unit: cores) × Collector CPU unit price + Memory usage (unit: GiB) × Collector memory unit price
Billing Item Description
Billing Item | Description |
Collector CPU | Cumulative calculation is based on the CPU usage and memory usage per hour. |
Collector memory | |
Fee Deduction Cycle
Bill per hour. TMP sends a billing push and settles costs daily based on your resource usage in the previous hour.
Collector Price
Non-finance zones in the Chinese mainland, such as Guangzhou, Shanghai, and Beijing.
Billing Item Name | Price (USD) |
Collector CPU | 0.014 USD/Cores/Hour |
Collector memory | 0.006 USD/GiB/Hour |
finance zones in the Chinese mainland + in the regions outside the Chinese mainland (Hong Kong (China), Macao (China), Taiwan (China), and overseas), such as Hong Kong (China)
Billing Item Name | Price (USD) |
Collector CPU | 0.017 USD/Cores/Hour |
Collector memory | 0.007 USD/GiB/Hour |
Billing Examples
Example 1:
Assuming a user in Guangzhou uses 2 CPU cores and 4 GiB of memory for an hour, the cost for this hour would be:2 × 0.014 + 4 × 0.006 = $0.052
Example 2:
Assuming a user in Hong Kong (China) uses 2 CPU cores and 4 GiB of memory for an hour, the cost for this hour would be:2 × 0.017 + 4 × 0.007 = $0.062
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No