All Products
Search
Document Center

Cloud Monitor:Billing overview

Last Updated:Feb 28, 2026

This topic describes the billing method, billing structure, and billing cycle of Managed Service for Prometheus.

Billing method

Managed Service for Prometheus uses the pay-as-you-go billing method. Resource plans are not available.

  • Pay-as-you-go billing is based on actual usage of each billable item, with payment following usage. Free quotas are provided each month.

  • The international site does not offer savings plans. If you require assistance, please submit a ticket.

Terms

The following terms are used throughout this topic to describe how billing is calculated.

Term

Description

basic metric

Managed Service for Prometheus classifies ingested metrics into two types: basic metrics and custom metrics.

The ingestion of basic metrics is free. Sources of basic metrics include basic metrics from Alibaba Cloud container service monitoring, basic metrics from the self-monitoring of Managed Service for Prometheus, and basic metrics from Realtime Compute for Apache Flink monitoring. For details about specific basic metrics, see Metrics.

custom metric

Metrics that fall outside the scope of basic metrics are considered custom metrics. Custom metrics incur metric ingestion fees, which are charged based on either write volume or reporting volume depending on the billing mode.

reporting volume (number of ingested samples)

When metrics are ingested into the Prometheus instance, the number of transmitted samples (also called data points) is counted. For example, the kube_node_status_allocatable_cpu_cores metric monitors the allocatable CPU cores for each node in a Kubernetes cluster. If your cluster contains 3 nodes, this metric generates 3 different time series. If each node is sampled every 15 seconds, the number of ingested samples within one minute is 3 x 60/15 = 12. The reporting volume for this metric in one minute is therefore 12 samples.

image.png

write volume (data size before compression)

When metrics are ingested into the Prometheus instance, the size of the transmitted data before compression is counted. For example, using the kube_node_status_allocatable_cpu_cores metric mentioned above, if each sample is 0.5 KB in size, the write volume for this metric in one minute is 12 x 0.5 = 6 KB.

Billing structure

Managed Service for Prometheus provides two services: a managed Prometheus service and the Container Monitoring service. The managed Prometheus service incurs Prometheus instance fees, while Container Monitoring incurs container monitoring fees. Container monitoring fees include cluster scale fees and Prometheus instance fees.

Prometheus instance fees

Prometheus instance fees cover the following billable items:

image

Container monitoring fees

Managed Service for Prometheus provides ready-to-use monitoring solutions for Alibaba Cloud container services in two editions: Container Monitoring Basic Edition and Pro Edition. The billing details are as follows.

Note

Only ACK Pro clusters support the activation of Container Monitoring Pro Edition. By default, other types of container clusters are limited to using Container Monitoring Basic Edition.

image

Billing cycle

Managed Service for Prometheus is billed on a daily cycle. The previous day's resource consumption is calculated starting at 00:00 the next day. Bills are typically generated by 08:00 on the day of deduction. Once the bill is issued, the system automatically deducts the billed amount from your account if your balance is sufficient. You can view your bills in the Expenses and Costs console and check your usage as described in Usage query.