Documentation ¶
Overview ¶
Package cadvisor contains a monitor that pulls cadvisor stats either directly from cadvisor or from the kubelet /stats endpoint that exposes cadvisor.
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
This section is empty.
Types ¶
type CHTTPConfig ¶
type CHTTPConfig struct { config.MonitorConfig // Where to find cAdvisor CAdvisorURL string `yaml:"cadvisorURL" default:"http://localhost:4194"` }
CHTTPConfig is the monitor-specific config for cAdvisor
type Cadvisor ¶
Cadvisor is the monitor that goes straight to the exposed cAdvisor port to get metrics
func (*Cadvisor) Configure ¶
func (c *Cadvisor) Configure(conf *CHTTPConfig) error
Configure the cAdvisor monitor
type KubeletStatsConfig ¶
type KubeletStatsConfig struct { config.MonitorConfig // Kubelet client configuration KubeletAPI kubelet.APIConfig `yaml:"kubeletAPI" default:""` // Whether to log the raw cadvisor response at the debug level for // debugging purposes. LogResponses bool `yaml:"logResponses" default:"false"` }
KubeletStatsConfig respresents config for the Kubelet stats monitor
type KubeletStatsMonitor ¶
KubeletStatsMonitor will pull container metrics from the /stats/ endpoint of the Kubelet API. This is the same thing that other K8s metric solutions like Heapster use and should eventually completely replace out use of the cAdvisor endpoint that some K8s deployments expose. Right now, this assumes a certain format of the stats that come off of the endpoints. TODO: Figure out if this is versioned and how to access versioned endpoints.
func (*KubeletStatsMonitor) Configure ¶
func (ks *KubeletStatsMonitor) Configure(conf *KubeletStatsConfig) error
Configure the Kubelet Stats monitor