Skip to content

Commit

Permalink
Merge pull request kubernetes-retired#776 from a-robinson/gke
Browse files Browse the repository at this point in the history
Clarify the doc about getting set up with Google Cloud Monitoring
  • Loading branch information
vishh committed Dec 9, 2015
2 parents f525f2a + ff8d3e5 commit 061eafb
Showing 1 changed file with 10 additions and 1 deletion.
11 changes: 10 additions & 1 deletion docs/google.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,13 @@

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

### Setup a Kubernetes cluster
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](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](https://github.com/kubernetes/kubernetes), if you haven't already. Ensure that `kubecfg.sh` is exported.

### Start all of the pods and services
Expand All @@ -20,5 +26,8 @@ To access the Google Cloud Monitoring dashboard go to: [https://app.google.stack

It is also possible to query the Google Cloud Monitoring data directly using their [custom metric read API](https://cloud.google.com/monitoring/v2beta2/timeseries/list).

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](https://cloud.google.com) and select 'Logs' under 'Monitoring' in your project. In the Logs dashboard, select `custom.googleapis.com` as the logs source.

0 comments on commit 061eafb

Please sign in to comment.