k3s/cluster/images/etcd-version-monitor
Davanum Srinivas 954996e231
Move from glog to klog
- Move from the old github.com/golang/glog to k8s.io/klog
- klog as explicit InitFlags() so we add them as necessary
- we update the other repositories that we vendor that made a similar
change from glog to klog
  * github.com/kubernetes/repo-infra
  * k8s.io/gengo/
  * k8s.io/kube-openapi/
  * github.com/google/cadvisor
- Entirely remove all references to glog
- Fix some tests by explicit InitFlags in their init() methods

Change-Id: I92db545ff36fcec83afe98f550c9e630098b3135
2018-11-10 07:50:31 -05:00
..
BUILD Move from glog to klog 2018-11-10 07:50:31 -05:00
Dockerfile
Makefile remove gcloud docker -- since it's deprecated 2018-02-28 00:24:27 -08:00
README.md Switch to k8s.gcr.io vanity domain 2018-02-07 21:14:19 -08:00
etcd-version-monitor.go Move from glog to klog 2018-11-10 07:50:31 -05:00
etcd-version-monitor.yaml In etcd-version-monitor, Remove grpc labels used only in etcd 3 format when translating metric back to 3.0 format 2018-02-15 15:35:51 -08:00

README.md

etcd-version-monitor

This is a tool for exporting etcd metrics and supplementing them with etcd server binary version and cluster version. These metrics are in prometheus format and can be scraped by a prometheus server. The metrics are exposed at the http://localhost:9101/metrics endpoint.

For etcd 3.1+, the go-grpc-prometheus metrics format, which backward incompatibly replaces the 3.0 legacy grpc metric format, is exposed in both the 3.1 format and in the 3.0. This preserves backward compatibility.

For etcd 3.1+, the --metrics=extensive must be set on etcd for grpc request latency metrics (etcd_grpc_unary_requests_duration_seconds) to be exposed.

RUNNING THE TOOL

To run this tool as a docker container:

  • make build
  • docker run --net=host -i -t k8s.gcr.io/etcd-version-monitor:test /etcd-version-monitor --logtostderr

To run this as a pod on the kubernetes cluster:

  • Place the 'etcd-version-monitor.yaml' in the manifests directory of kubelet on the master machine.

Note: This tool has to run on the same machine as etcd, as communication with etcd is over localhost.

VERIFYING THE TOOL