Skip to content

Kubernetes

Connect Kubernetes consumption metrics with Exivity to understand container resource usage, allocate costs across pods and namespaces, and support Kubernetes FinOps, showback, chargeback, and billing.

At a glance

Product
Hypermeter and Exivity Core
Source and connection
Prometheus (recommended); cAdvisor and the Kubelet API are also supported
Data collected
Pod, container, namespace and project consumption metrics

Exivity integrates with Kubernetes environments to provide detailed visibility into container and workload consumption for cost allocation, reporting, and billing.

Exivity can retrieve Kubernetes consumption metrics using Prometheus, as well as metrics available through cAdvisor and the Kubelet API. Prometheus is generally recommended because it provides a rich source of consumption data for billing and cost management use cases.

Consumption can be analyzed across Kubernetes dimensions including pods, containers, namespaces, and projects, helping organizations understand how shared container infrastructure is being consumed by different applications, teams, customers, or services.

This data can then be enriched with organizational and business context and combined with custom rates and charging rules. Enterprises can use this information for Kubernetes cost allocation, showback, chargeback, and FinOps, while service providers can use the same consumption data as the foundation for customer billing.

Kubernetes metrics can also be combined with public cloud, private cloud, virtualization, and other infrastructure data in Exivity. This is particularly useful where Kubernetes workloads span multiple environments and organizations need a consolidated view of costs rather than a Kubernetes-only perspective.

See this integration on your own data.

A demo scoped to your platform, run by an engineer who has connected it before. Bring one account or source; leave with a rated report.