Collected metrics and dimensions for Kubernetes ๐
The following sections list the collected metrics when you use the default configuration for the Collector for Kubernetes in host monitoring (agent) mode.
The Collector processes collected data as configured in your pipelines. Therefore, metrics that are imported by receivers might be excluded further into the pipeline by other components. For instance, the SignalFx exporter, included in the default Collector configuration, drops certain metrics and applies translation rules that impact the metrics the Collector sends to Splunk Observability Cloud.
Learn more about the Collectorโs configuration and data processing at:
Note
In addition to the metrics shown on this page, most Collector instances also send metrics from the Kubernetes cluster receiver, which are an important part of monitoring any Kubernetes installation. Refer to that page as well as the metrics listed here.
For the Collectorโs internal metrics, see Internal metrics of the Collector.
Container level metrics and dimensions ๐
Caution
The Translated? column indicates whether the metric is translated by the SignalFx exporter.
The Exported? column indicates if the metric is finally sent to Splunk Observability Cloud after going through the Collector pipelines.
Metric name |
Metric description |
Attributes |
Translated? |
Exported? |
---|---|---|---|---|
|
Container CPU utilization |
Yes |
Yes |
|
|
Container CPU time |
No |
No |
|
|
Container memory available |
No |
No |
|
|
Container memory usage |
No |
No |
|
|
Container memory rss |
No |
No |
|
|
Container memory |
No |
No |
|
|
Container memory |
No |
No |
|
|
Container memory |
No |
No |
|
|
Container filesystem available |
No |
Yes |
|
|
Container filesystem capacity |
No |
Yes |
|
|
Container filesystem usage |
No |
Yes |
|
|
Container |
No |
Yes |
|
|
Container |
No |
Yes |
|
|
Container |
No |
No |
|
|
Container |
No |
No |
|
|
Container |
No |
Yes |
|
|
Container |
No |
Yes |
|
|
Container |
No |
Yes |
|
|
Container |
No |
No |
|
|
Container |
No |
No |
Pod level metrics and dimensions ๐
Caution
The Exported? column indicates if the metric is finally sent to Splunk Observability Cloud after going through the Collector pipelines.
Metric name |
Metric description |
Attributes |
Exported? |
---|---|---|---|
|
Pod CPU time |
No |
|
|
Pod CPU utilization |
No |
|
|
Pod filesystem available |
No |
|
|
Pod filesystem capacity |
No |
|
|
Pod filesystem usage |
No |
|
|
Pod memory available |
No |
|
|
Pod memory |
No |
|
|
Pod memory |
No |
|
|
Pod memory rss |
No |
|
|
Pod memory usage |
No |
|
|
Pod memory |
No |
|
|
Pod network errors |
|
Yes |
|
Pod network IO |
|
Yes |
|
Information on the pod status |
Yes |
Node level metrics and dimensions ๐
Caution
The Translated? column indicates whether the metric is translated by the SignalFx exporter.
The Exported? column indicates if the metric is finally sent to Splunk Observability Cloud after going through the Collector pipelines.
Metric name |
Metric description |
Attributes |
Exported? |
---|---|---|---|
|
Node condition |
No |
|
|
Node CPU time |
No |
|
|
Node CPU utilization |
No |
|
|
Node filesystem available |
No |
|
|
Node filesystem capacity |
No |
|
|
Node filesystem usage |
No |
|
|
Node memory available |
No |
|
|
Node memory |
No |
|
|
Node memory |
No |
|
|
Node memory rss |
No |
|
|
Node memory usage |
No |
|
|
Node memory |
No |
|
|
Node network errors |
|
No |
|
Node network IO |
|
No |
|
System CPU time |
No |
|
|
Percentage of CPU time broken down by different states |
|
Yes |
|
Filesystem bytes used |
|
Yes |
|
Fraction of filesystem bytes used |
|
Yes |
|
Average CPU Load over 1 minute |
Yes |
|
|
Average CPU Load over 5 minutes |
Yes |
|
|
Average CPU Load over 15 minutes |
Yes |
|
|
Bytes of memory in use |
|
Yes |
|
Percentage of memory bytes in use |
|
Yes |
|
Swap (Unix) or pagefile (Windows) utilization |
Yes |
Node level metrics and dimensions after translation ๐
Caution
The Exported? column indicates if the metric is finally sent to Splunk Observability Cloud after going through the Collector pipelines.
Note
These metrics are compatible with the SignalFx exporter.
Metric name |
Metric description |
Attributes |
Exported? |
---|---|---|---|
|
CPU time in centicores spent in any state other than those in the table |
Yes |
|
|
CPU time in centicores spent while servicing hardware interrupts |
Yes |
|
|
CPU time in centicores spent in userspace running |
Yes |
|
|
CPU time in centicores spent while servicing software interrupts |
Yes |
|
|
CPU time in centicores spent waiting for a hypervisor to service requests from other virtual machines |
Yes |
|
|
CPU time in centicores spent running in the kernel |
Yes |
|
|
CPU time in centicores spent running in userspace |
Yes |
|
|
CPU time in centicores spent idle while waiting for an I/O operation to complete |
Yes |
|
|
The number of logical processors on the host |
Yes |
|
|
Percent of CPU used on this host |
Yes |
|
|
Percent of disk space utilized on all volumes on this host |
Yes |
|
|
Percent of disk used on this volume |
|
Yes |
|
Total bytes of system memory on the system |
Yes |
|
|
Percent of memory in use on this host |
Yes |
|
|
Total amount of inbound and outbound network traffic on this host, in bytes |
Yes |
|
|
Total CPU usage of the process in seconds |
|
Yes |
Volume level metrics and dimensions ๐
Caution
The Exported? column indicates if the metric is finally sent to Splunk Observability Cloud after going through the Collector pipelines.
Metric name |
Metric description |
Attributes |
Exported? |
---|---|---|---|
|
The number of available bytes in the volume |
Yes |
|
|
The number of capacity bytes in the volume |
Yes |
Control plane metrics ๐
To see the control plane metrics the Collector provides, see:
The following distributions support control plane metrics configuration:
Kubernetes 1.22 (kops created)
OpenShift version 4.9
For information about control plane metrics, see Configure control plane metrics.
Other metrics ๐
Caution
The Exported? column indicates if the metric is finally sent to Splunk Observability Cloud after going through the Collector pipelines.
Other available metrics include:
Metric name |
Exported? |
---|---|
|
Yes |
|
Yes |
|
Yes |
|
Yes |
|
Yes |
|
Yes |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
Yes |
|
Yes |
|
Yes |
|
Yes |
|
Yes |
|
Yes |
|
Yes |
|
No |
|
No |
|
No |
|
No |
|
Yes |
|
Yes |
|
Yes |
|
Yes |
Standard resource dimensions ๐
Name |
Type |
Description |
---|---|---|
|
string |
The name of the node |
|
string |
The UID of the pod |
|
string |
The name of the pod |
|
string |
The name of the namespace that the pod is running in |
|
string |
Container name used by container runtime |
|
string |
Container id used to identify container |
|
string |
The name of the volume |
|
string |
The type of the volume |
|
string |
The name of the Persistent Volume Claim |
|
string |
The id of the AWS Volume |
|
string |
The filesystem type of the volume |
|
string |
The partition in the volume |
|
string |
The name of the persistent disk in GCE |
|
string |
The endpoint name that details Glusterfs topology |
|
string |
Glusterfs volume path |