Skip to content

Latest commit

 

History

History
33 lines (22 loc) · 2.04 KB

google.md

File metadata and controls

33 lines (22 loc) · 2.04 KB

Running Heapster in Kubernetes with a Google Cloud Monitoring and Google Cloud Logging backend

The Google Cloud Monitoring and Logging backends only works in Google Compute Engine today.

Note: this doc is intended for people setting up their own Kubernetes environment. If you're using Google Container Engine, Heapster will already be set up for you with much tighter integration into Google Cloud Monitoring, and all your clusters' metrics and events will be organized for you at https://app.google.stackdriver.com/gke. Please allow up to an hour after your cluster is created for it to show up there.

Set up a Kubernetes cluster

Bring up a Kubernetes cluster, if you haven't already. Ensure that kubecfg.sh is exported.

Start all of the pods and services

Start the Heapster service on the cluster:

$ kubectl.sh create -f deploy/kube-config/google/

Heapster metrics are now being exported to Google Cloud Monitoring as custom metrics. Heapster events are now being exported to Google Cloud Logging as custom logs.

Metrics Dashboard

To access the Google Cloud Monitoring dashboard go to: https://app.google.stackdriver.com/. Create a new dashboard and add the desired charts. Select the Custom Metric Resource Type and all Heapster metrics are under the kubernetes.io namespace. You can narrow down the query by the metric labels provided.

It is also possible to query the Google Cloud Monitoring data directly using their custom metric read API.

Note: as mentioned in the intro, this section only applies if you've set up Heapster as described in this doc, not if you're using Container Engine.

Events Dashboard

To access events via Google Cloud Logging dashboard go to Google Developer Console and select 'Logs' under 'Monitoring' in your project. In the Logs dashboard, select custom.googleapis.com as the logs source.