关于OpenShift 3.1.1 Pod概览中各资源指标Y轴单位的咨询
Hey there, let's unpack your questions about the metric units in OpenShift 3.1.1's Pod Overview page and what happens when you jump to Prometheus from the memory metrics:
Metric Units in OpenShift 3.1.1 Pod Overview
RAM Metric: What does "B" stand for?
- The "B" on the RAM metric's Y-axis is short for Bytes. This is the base unit for memory tracking here—while the UI might auto-scale to KB, MB, or GB as memory usage grows, the underlying raw value is measured in bytes.
CPU Shares: Y-axis Unit
- CPU Shares are measured in shares (this is the official unit, though the UI might not always label it explicitly). It’s a relative weighting system: a Pod with 2000 shares will get twice the CPU allocation of a Pod with 1000 shares when cluster resources are constrained.
Filesystem Metric: Is the unit MB?
- You’re spot on! The filesystem usage metric in the Pod Overview UI uses Megabytes (MB) as its primary displayed unit. It tracks used/available storage for the Pod’s mounted volumes, scaled to MB for readability (raw data is stored in bytes, but the UI presents it in MB).
What appears when you jump to Prometheus from the memory metric?
When you click the memory metric to navigate to Prometheus, you’ll see a few key things:
- A pre-configured PromQL query tailored to your Pod’s memory usage, for example:
container_memory_usage_bytes{pod="your-pod-name", namespace="your-namespace"} - A time-series graph that mirrors the memory trend shown in OpenShift’s Pod Overview, spanning the same timeframe
- Detailed metadata labels (like Pod name, container name, namespace, and node) attached to the metric
- Controls to adjust the time range, add additional metrics to the graph, or export the metric data
内容的提问来源于stack exchange,提问作者william007
相关产品推荐
相关产品推荐

