grafana/docs/sources/datasources/google-cloud-monitoring/_index.md

aliases	description	keywords	menuTitle	title	weight
../data-sources/google-cloud-monitoring/ ../data-sources/google-cloud-monitoring/preconfig-cloud-monitoring-dashboards/ ../features/datasources/cloudmonitoring/ ../features/datasources/stackdriver/ cloudmonitoring/ preconfig-cloud-monitoring-dashboards/	Guide for using Google Cloud Monitoring in Grafana	grafana stackdriver google guide cloud monitoring	Google Cloud Monitoring	Google Cloud Monitoring data source	350

Google Cloud Monitoring data source

Grafana ships with built-in support for Google Cloud Monitoring. This topic describes queries, templates, variables, and other configuration specific to the Google Cloud Monitoring data source.

Note: Before Grafana v7.1, Google Cloud Monitoring was referred to as Google Stackdriver.

For instructions on how to add a data source to Grafana, refer to the [administration documentation]({{< relref "../../administration/data-source-management/" >}}). Only users with the organization administrator role can add data sources.

Once you've added the Google Cloud Monitoring data source, you can [configure it]({{< relref "#configure-the-data-source" >}}) so that your Grafana instance's users can create queries in its [query editor]({{< relref "./query-editor/" >}}) and apply [annotations]({{< relref "#annotations" >}}) when they [build dashboards]({{< relref "../../dashboards/build-dashboards/" >}}) and use [Explore]({{< relref "../../explore/" >}}).

Configure the data source

To access the data source configuration page:

1. Hover the cursor over the Configuration (gear) icon.
2. Select Data Sources.
3. Select the Google Cloud Monitoring data source.

Set the data source's basic configuration options carefully:

Name	Description
Name	Sets the name you use to refer to the data source in panels and queries.
Default	Sets whether the data source is pre-selected for new panels.

Configure Google authentication

Before you can request data from Google Cloud Monitoring, you must configure authentication. All requests to Google APIs are performed on the server-side by the Grafana backend.

For authentication options and configuration details, refer to [Google authentication]({{< relref "./google-authentication/" >}}).

When configuring Google authentication, note these additional Google Cloud Monitoring-specific steps:

Configure a GCP Service Account

When you [create a Google Cloud Platform (GCP) Service Account and key file]({{< relref "./google-authentication/#create-a-gcp-service-account-and-key-file" >}}), the Service Account must have the Monitoring Viewer role (Role > Select a role > Monitoring > Monitoring Viewer):

{{< figure src="/static/img/docs/v71/cloudmonitoring_service_account_choose_role.png" max-width="600px" class="docs-image--no-shadow" caption="Choose role" >}}

Grant the GCE Default Service Account scope

If Grafana is running on a Google Compute Engine (GCE) virtual machine, then when you [Configure a GCE Default Service Account]({{< relref "./google-authentication/#configure-a-gce-default-service-account" >}}), you must also grant that Service Account access to the "Cloud Monitoring API" scope.

Enable necessary Google Cloud Platform APIs

Before you can request data from Google Cloud Monitoring, you must first enable necessary APIs on the Google end.

1. Open the Monitoring and Cloud Resource Manager API pages:

   • Monitoring API
   • Cloud Resource Manager API

2. On each page, click the Enable button.

   {{< figure src="/static/img/docs/v71/cloudmonitoring_enable_api.png" max-width="450px" class="docs-image--no-shadow" caption="Enable GCP APIs" >}}

Provision the data source

You can define and configure the data source in YAML files as part of Grafana's provisioning system. For more information about provisioning, and for available configuration options, refer to [Provisioning Grafana]({{< relref "../../administration/provisioning/#data-sources" >}}).

Provisioning examples

Using the JWT (Service Account key file) authentication type:

apiVersion: 1

datasources:
  - name: Google Cloud Monitoring
    type: stackdriver
    access: proxy
    jsonData:
      tokenUri: https://oauth2.googleapis.com/token
      clientEmail: stackdriver@myproject.iam.gserviceaccount.com
      authenticationType: jwt
      defaultProject: my-project-name
    secureJsonData:
      privateKey: |
        -----BEGIN PRIVATE KEY-----
        POSEvQIBADANBgkqhkiG9w0BAQEFAASCBKcwggSjAgEAAoIBAQCb1u1Srw8ICYHS
        ...
        yA+23427282348234=
        -----END PRIVATE KEY-----        

Using GCE Default Service Account authentication:

apiVersion: 1

datasources:
  - name: Google Cloud Monitoring
    type: stackdriver
    access: proxy
    jsonData:
      authenticationType: gce

Import pre-configured dashboards

The Google Cloud Monitoring data source ships with pre-configured dashboards for some of the most popular GCP services. These curated dashboards are based on similar dashboards in the GCP dashboard samples repository.

{{< figure src="/static/img/docs/google-cloud-monitoring/curated-dashboards-7-4.png" class="docs-image--no-shadow" max-width="650px" caption="Curated dashboards for Google Cloud Monitoring" >}}

To import curated dashboards:

1. Navigate to the data source's [configuration page]({{< relref "#configure-the-data-source" >}}).

2. Select the Dashboards tab.

   This displays the curated selection of importable dashboards.

3. Select Import for the dashboard to import.

The dashboards include a [template variable]({{< relref "./template-variables/" >}}) populated with the projects accessible by the configured [Service Account]({{< relref "./google-authentication/" >}}) each time you load the dashboard. After Grafana loads the dashboard, you can select a project from the dropdown list.

To customize an imported dashboard:

To customize one of these dashboards, we recommend that you save it under a different name. If you don't, upgrading Grafana can overwrite the customized dashboard with the new version.

Query the data source

The Google Cloud Monitoring query editor helps you build two types of queries: Metric and Service Level Objective (SLO).

For details, refer to the [query editor documentation]({{< relref "./query-editor/" >}}).

Use template variables

Instead of hard-coding details such as server, application, and sensor names in metric queries, you can use variables. Grafana lists these variables in dropdown select boxes at the top of the dashboard to help you change the data displayed in your dashboard. Grafana refers to such variables as template variables.

For details, see the [template variables documentation]({{< relref "./template-variables/" >}}).