diff --git a/public/app/plugins/datasource/cloud-monitoring/components/ConfigEditor/ConfigEditor.tsx b/public/app/plugins/datasource/cloud-monitoring/components/ConfigEditor/ConfigEditor.tsx index 745ad6eee16..5e0fd90ca16 100644 --- a/public/app/plugins/datasource/cloud-monitoring/components/ConfigEditor/ConfigEditor.tsx +++ b/public/app/plugins/datasource/cloud-monitoring/components/ConfigEditor/ConfigEditor.tsx @@ -1,5 +1,5 @@ import React, { PureComponent } from 'react'; -import { Select, FieldSet, InlineField, Alert } from '@grafana/ui'; +import { Select, InlineField, Alert } from '@grafana/ui'; import { DataSourcePluginOptionsEditorProps, onUpdateDatasourceJsonDataOptionSelect } from '@grafana/data'; import { AuthType, authTypes, CloudMonitoringOptions, CloudMonitoringSecureJsonData } from '../../types'; import { JWTConfig } from './JWTConfig'; @@ -17,59 +17,9 @@ export class ConfigEditor extends PureComponent { return ( <> -
-
-

Google Cloud Monitoring Authentication

-

- There are two ways to authenticate the Google Cloud Monitoring plugin - either by uploading a Service - Account key file or by automatically retrieving credentials from the Google metadata server. The latter - option is only available when running Grafana on a GCE virtual machine. -

- -
Uploading a Service Account Key File
-

- There are two ways to authenticate the Google Cloud Monitoring plugin. You can upload a Service Account - key file or automatically retrieve credentials from the Google metadata server. The latter option is only - available when running Grafana on a GCE virtual machine. -

-

- The Monitoring Viewer role provides all the permissions that Grafana needs. The following - API needs to be enabled on GCP for the data source to work:{' '} - - Monitoring API - -

- -
GCE Default Service Account
-

- If Grafana is running on a Google Compute Engine (GCE) virtual machine, it is possible for Grafana to - automatically retrieve the default project id and authentication token from the metadata server. In order - for this to work, you need to make sure that you have a service account that is setup as the default - account for the virtual machine and that the service account has been given read access to the Google - Cloud Monitoring Monitoring API. -

- -

- Detailed instructions on how to create a Service Account can be found{' '} - - in the documentation. - -

-
-
- -
- +

Authentication

+
+