Kubernetes Onboarding Questionnaire

Q1: Why do we need Prometheus?

Prometheus is used to scrape usage metrics for Kubernetes resources, enabling efficient resource monitoring and cost analysis.

Q2: What metrics do we scrape using Prometheus?

The appliance reads the metrics below from your Prometheus, one hour of data at a time.

Workloads

container_cpu_usage_seconds_total
container_memory_working_set_bytes
kube_pod_container_resource_requests
kube_pod_container_resource_limits
kube_pod_owner
kube_pod_labels
kube_pod_status_phase

Nodes

kube_node_info
kube_node_status_capacity

Storage and volumes

container_fs_reads_bytes_total
container_fs_writes_bytes_total
kube_persistentvolume_info
kube_persistentvolume_created
kube_persistentvolume_capacity_bytes
kube_persistentvolumeclaim_info
kube_persistentvolumeclaim_created
kube_persistentvolumeclaim_resource_requests_storage_bytes
kube_pod_spec_volumes_persistentvolumeclaims_info
kubelet_volume_stats_used_bytes
kubelet_volume_stats_capacity_bytes

GPU (collected only for NVIDIA GPU nodes that expose these metrics through the DCGM exporter)

DCGM_FI_DEV_GPU_UTIL
DCGM_FI_DEV_MEM_COPY_UTIL
DCGM_FI_DEV_FB_USED
DCGM_FI_DEV_FB_FREE
DCGM_FI_DEV_SM_CLOCK
DCGM_FI_DEV_GPU_TEMP
DCGM_FI_DEV_POWER_USAGE
DCGM_FI_DEV_TOTAL_ENERGY_CONSUMPTION

Q3: How often is Kubernetes cost data refreshed?

Cost data is refreshed once every 24 hours.

Q4: What is Split/Ratio in Kubernetes on Cloud?

Split/Ratio is a method used to distribute the cost of shared Kubernetes resources (e.g., nodes, clusters) among multiple workloads, namespaces, or teams based on defined proportions. Currently, we are following industry-standard ratios and setting the CPU and memory ratio as 87:13 by default. This ratio is applied automatically, and there is currently no setting in the Mavvrik console to change it. If you need a different ratio, contact your Mavvrik representative.