Currently, when you use the TMP service, EKS clusters and CLB resources will be created under your account. These resources and TMP are pay-as-you-go. This document describes resource usage details when you use TMP.
The capability of Billable Metric Collection Rate has been launched for TMP, which helps you estimate the cost of monitoring by instance, cluster, target, and metric.
After each TMP instance is created, a pay-as-you-go EKS cluster will be created under your account for data collection. View the resource information on the elastic cluster list page as shown below:
The name of the EKS cluster is the TMP instance ID, and the cluster description states that "For TMP use only. Do not modify or delete".
The billing mode is pay-as-you-go. For more information, see Product Pricing.
The EKS cluster automatically scales according to the monitoring size. The relationship between the monitoring size and the EKS cluster cost is as shown below:
|Reported Instantaneous Series||Estimated EKS Resources Required||Published Price/Day|
|<500,000||1.25 cores, 1.6 GiB||0.35 USD|
|1 million||0.5 core, 1.5 GiB*2||1.46 USD|
|5 million||1 core, 3 GiB*3||2.93 USD|
|20 million||1 core, 6 GiB*5||7.98 USD|
|30 million||1 core, 6 GiB*8||12.77 USD|
Sample EKS cluster costs are as follows:
The EKS cluster used for a newly initialized TMP instance consumes 1.25 CPU cores and 1.5 GiB memory. The estimated published price per day is 0.0319 x 24 + 0.0132 x 24 = 1.0824 USD.
When you use TMP to associate the cluster monitoring container service, a private network CLB instance will be created under your account for network connectivity between the collector and the cluster.
If you associate an edge cluster or another cluster that is not connected, a public network CLB will be created for network connectivity.
To access the Grafana service over the public network, you need to create a public network CLB instance.
These CLB resources will be charged. You can view the resource information of the created public network CLB instances in the CLB console.
This resource is pay-as-you-go. For more information, see Billing for Bill-by-IP Accounts.
Currently, you cannot delete resources in their respective consoles. For example, when you terminate TMP instances in the TMP console, all relevant resources will also be terminated. Tencent Cloud does not repossess TMP instances proactively. If you no longer use TMP, you need to delete the instances promptly to avoid additional charges.