Billing Items

Billing Description

You will be billed based on reported custom metrics. For details, see Table 1. For AOM 2.0, basic metrics are free of charge, but reported custom metrics are not.

**Table 1** Pay-per-use prices of billing items
Billing Item	Description	Price
Reported custom metrics	The number of reported custom metrics refers to the number of sampling points. It is calculated based on the open-source Prometheus data model. A sampling point data record contains the metric name, label set, sampling timestamp, and value. Sampling points are logically organized on a time line. For example, the kube_node_status_allocatable_cpu_cores metric monitors the number of CPU cores that can be allocated to each node in a Kubernetes cluster. If your cluster contains three nodes, the sampling points are distributed on three different timelines. If the sampling period of each node is 15s, the total number of reported sampling point data records within 1 minute can be calculated as follows: 3 x (60/15) = 12. Scenarios where custom metrics are reported: Why Are Additional Fees Incurred After Prometheus Instances Are Connected?	0–150 million metrics: $0.1 USD/million metrics/day 150–600 million metrics: $0.07 USD/million metrics/day 600–1,200 million metrics: $0.05 USD/million metrics/day > 1,200 million metrics: $0.04 USD/million metrics/day

Billing Examples

The following uses reported custom metrics as an example. The prices mentioned in the following are only for reference. For details, see Price Calculator.

Assume that you have one server and 800 million metrics are reported every day. You will be billed based on three price ranges. The fee is calculated as follows: