WARNING: Version 6.0 of Metricbeat has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
This functionality is in beta and is subject to change. The design and code is less mature than official GA features and is being provided as-is with no warranties. Beta features are not subject to the support SLA of official GA features.
All metricsets with the
state_ prefix require
hosts field pointing to kube-stat-metrics
service within the cluster, while the rest should be pointed to kubelet service. Check the
example configuration on how to do it.
The Kubernetes module supports the standard configuration options that are described in Specify which modules to run. Here is an example configuration:
metricbeat.modules: # Node metrics, from kubelet: - module: kubernetes metricsets: - node - system - pod - container - volume period: 10s hosts: ["localhost:10255"] # State metrics from kube-state-metrics service: - module: kubernetes enabled: false metricsets: - state_node - state_deployment - state_replicaset - state_pod - state_container period: 10s hosts: ["kube-state-metrics:8080"] # Kubernetes events - module: kubernetes enabled: false metricsets: - event
The following metricsets are available: