--- title: "Kubernetes Monitoring pricing | Grafana Cloud documentation" description: "Learn how Kubernetes Monitoring bills for active host and container hours, and how usage is calculated." --- > For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt). # Kubernetes Monitoring pricing Kubernetes Monitoring bills on active host hours and active container hours in a calendar month. Usage is metered from `kube-state-metrics`, so what you’re billed for depends on what that exporter reports. For current rates, refer to the [pricing page](/pricing/#kubernetes-monitoring). ## How Kubernetes Monitoring is billed Billing starts when a host or container sends `kube-state-metrics` to Grafana Cloud after Kubernetes Monitoring is [activated](/docs/grafana-cloud/observe-and-act/monitor-infrastructure/kubernetes-monitoring/configuration/activate/). Two meters run in parallel: - **Host hours** for each active Kubernetes node. - **Container hours** for each active container. [Diagram of a Node, Pod, and its containers](/media/docs/grafana-cloud/k8s/host_container.png) Kubernetes Monitoring usage means gathering metrics for Kubernetes infrastructure components, such as: - Whether a Pod or container is running and healthy - Whether the workload replicas match the actual replicas - CPU, memory, network, and storage for clusters, nodes, and so on Telemetry from other products running on the same cluster isn’t Kubernetes Monitoring usage and is billed separately. That includes an integration such as NGINX, an application monitored by Application Observability, and Frontend Observability. ## Definitions **Host:** The Kubernetes node, whether it’s a virtual machine or a physical machine, as reported by `kube-state-metrics`. A Pod isn’t a host. Pods are groups of one or more containers that run within nodes, and the node is the host. **Container:** A container running on an active node and reported by `kube-state-metrics`. **Active:** A host or container is active if `kube-state-metrics` has reported data for it within the last 15 minutes. ## How usage is calculated Grafana meters hosts only while they’re active rather than charging for the whole month. Metering begins as soon as one minute of host or container activity is captured, and the minimum tracked is 15 minutes plus the active time: - Container A monitored for 2 minutes: 15 + 2 = 17 minutes billed - Container B monitored for 43 minutes: 15 + 43 = 58 minutes billed - Node C monitored for 70 minutes: 15 + 70 = 85 minutes billed Billable hours are the number of hosts or containers multiplied by the hours each is active. One host active for 24 hours a day across a 30-day month is: text ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```text 1 host x 24 hours x 30 days = 720 host hours ``` This example assumes the default of scraping one data point per minute. ## Special considerations ### Windows nodes If you run Windows nodes in a Kubernetes cluster, you’re billed for host hours when `kube-state-metrics` is present in the same cluster. ### Telemetry that isn’t kube-state-metrics If you use OpenTelemetry-style telemetry or another collection method such as VictoriaMetrics with Kubernetes Monitoring, the result is a partial or empty dataset. Without data from the `kube-state-metrics` exporter, active nodes and containers can’t be detected, and you aren’t billed for host hours. ### Which billing plan applies to you Kubernetes Monitoring has moved through three billing models. Which one applies depends on your customer type and when you started. **Customers who’s plans started after February 13, 2026**, whether self-serve or contract, are billed on active host and container hours, with no credits applied for telemetry use. **Customers who’s plans started between September 17, 2024 and February 13, 2026** are billed on active host and container hours, and the plan includes credits for telemetry. Refer to [Telemetry credits](#telemetry-credits). **Customers who’s plans started before September 17, 2024** are billed differently depending on customer type. Self-serve customers are billed for active billable series based on the underlying metrics generated, and stay on that model unless they migrate. Contact Support to move to the hourly model. Contract customers work with their account team to transition. ### Telemetry credits On the plan that includes credits, a credit of 1 billable series per active host hour and 0.10 billable series per active container hour is applied to your monthly invoice. [Diagram showing credits for an active Node and container](/media/docs/grafana-cloud/k8s/credit-bill-series.png) In the following example, the account had 2,700 billable series over the included usage, and 2,000 credits were applied to that overage. Credits apply to any metrics ingestion. [Diagram showing credits applied to Kubernetes Monitoring metrics](/media/docs/grafana-cloud/k8s/credit-example-1.png) In the next example, the account had 2,700 billable series unrelated to Kubernetes Monitoring. [Diagram showing credits applied to metrics not generated by Kubernetes Monitoring](/media/docs/grafana-cloud/k8s/credit-example-2.png) ### Included usage In the Cost Management and Billing app you might see *included host hours* or *included container hours*. This is the usage included with Grafana Cloud Pro and Advanced plans. If you exceed it, standard metric ingestion pricing applies to metrics gathered beyond the included amount. ## View your usage 1. In your Grafana Cloud stack, go to **Cost Management and Billing > Usage**. 2. Under **Product Breakdown**, select **Kubernetes Containers** for container usage, or **Kubernetes Hosts** for host usage. ## Related - [Kubernetes Monitoring pricing page](/pricing/#kubernetes-monitoring) - [Reduce Kubernetes Monitoring metrics costs](/docs/grafana-cloud/platform/cost-management-and-billing/analyze-costs/reduce-costs/metrics-costs/client-side-filtering/)