-
Notifications
You must be signed in to change notification settings - Fork 41.5k
Closed
Labels
area/introspectionarea/monitoringpriority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
Description
Some time back, we made decision to switch to GCM for monitoring, and GCL for logging for kubernetes clusters on GCE. But for logging, we still deploy Elasticsearch and Kibana services, but stop deploying InfluxDB and Grafana dashboard for monitoring. Given GCM is not completely ready yet, should we re-consider the decision for 1.0 release here?
$ cluster/kubectl.sh cluster-info
Kubernetes master is running at https://130.211.141.142
Elasticsearch is running at https://130.211.141.142/api/v1beta3/proxy/namespaces/default/services/elasticsearch-logging
Kibana is running at https://130.211.141.142/api/v1beta3/proxy/namespaces/default/services/kibana-logging
KubeDNS is running at https://130.211.141.142/api/v1beta3/proxy/namespaces/default/services/kube-dns
Metadata
Metadata
Assignees
Labels
area/introspectionarea/monitoringpriority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.