Skip to content

Commit

Permalink
Merge pull request #87 from GoogleCloudPlatform/adc-gcloud
Browse files Browse the repository at this point in the history
Update README.md
  • Loading branch information
jmdobry committed Mar 22, 2016
2 parents f0b511d + 644d49c commit 89d2937
Showing 1 changed file with 35 additions and 10 deletions.
45 changes: 35 additions & 10 deletions monitoring/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,22 +6,47 @@ Monitoring API to retrieve API data.
`create_custom_metric.js` demonstrates how to create a custom metric, write a timeseries value to it,
and read it back.

## Prerequisites to run locally:

Go to the [Google Developers Console](https://console.developer.google.com).
# Run locally

* Go to API Manager -> Credentials and click New Credential in the Google Developers Console.
[or click here ]{https://console.developers.google.com/project/_/apiui/credential/serviceaccount)
Select a JSON-format key, which will be downloaded to your computer. The key file must be located on the computer(s) from which you will access the Monitoring API. Access to the file should be restricted so that only trusted people can read the key.
Create local credentials by running the following command and following the oauth2 flow:

```
export GOOGLE_APPLICATION_CREDENTIALS=~/Downloads/<project-id>-0123456789abcdef.json
```
gcloud beta auth application-default login

Then to run:

# Run locally

npm install
node list_resources.js <YOUR-PROJECT-ID>
node create_custom_metric.js <YOUR-PROJECT-ID>


## Running on GCE, GAE, or other environments

On Google App Engine, the credentials should be found automatically.

On Google Compute Engine, the credentials should be found automatically, but require that
you create the instance with the correct scopes.

gcloud compute instances create --scopes="https://www.googleapis.com/auth/cloud-platform,https://www.googleapis.com/auth/compute,https://www.googleapis.com/auth/compute.readonly" test-instance

If you did not create the instance with the right scopes, you can still upload a JSON service
account and set GOOGLE_APPLICATION_CREDENTIALS as described below.


## Using a Service Account

In non-Google Cloud environments, GCE instances created without the correct scopes, or local
workstations if the `gcloud beta auth application-default login` command fails, use a Service
Account by doing the following:

* Go to API Manager -> Credentials
* Click 'New Credentials', and create a Service Account or [click here](https://console.cloud.google
.com/project/_/apiui/credential/serviceaccount)
Download the JSON for this service account, and set the `GOOGLE_APPLICATION_CREDENTIALS`
environment variable to point to the file containing the JSON credentials.


export GOOGLE_APPLICATION_CREDENTIALS=~/Downloads/<project-id>-0123456789abcdef.json



0 comments on commit 89d2937

Please sign in to comment.