Connect to Google Cloud Platform: Guided setup and other options 🔗
You can connect your GCP account and send data to Splunk Observability Cloud with the following methods:
注釈
Before you connect, make sure to read GCP authentication, permissions and supported regions.
Connect to GCP using the guided setup 🔗
Follow these steps to connect to GCP:
1. Define a role for your GCP service account 🔗
Use GCP’s Viewer role as it comes with the permissions you need for most scenarios.
To customize the permissions for your role refer to GCP role permissions.
2. Configure GCP 🔗
To configure your GCP service:
Log into your GCP account and select the project you want to monitor in the GCP web console.
サイドバーから を選択し、次に を選択します。
Go to Create Service Account at the top of the screen, complete the following fields, and select CREATE.
Service account name. Enter
Splunk.Service account ID. This field autofills after you enter
Splunkfor Service account name.Service account description. Enter the description for your service account.
(オプション）このサービスアカウントに選択したプロジェクトへのアクセス権を付与するロールを選択し、CONTINUE を選択します。
Activate Key type JSON, and select CREATE. A new service account key JSON file is then downloaded to your computer. You will need this key to authenticate in Splunk Observability Cloud.
In a new window or tab, go to Cloud Resource Manager API , and activate the Cloud Resource Manager API. You need to activate this API so Splunk Observability Cloud can use it to validate permissions on the service account keys.
注釈
複数のGCPプロジェクトを監視するには、プロジェクトごとにこのセクションで説明する手順を繰り返します。
3. Connect to Splunk Observability Cloud and start the integration 🔗
By default, Splunk Observability Cloud monitors all supported services, and any new services added later are also monitored. When you set integration parameters, you can choose to import metrics from a subset of the available services.
Log in to Splunk Observability Cloud and open the Google Cloud Platform guided setup . Optionally, you can navigate to the guided setup on your own:
In the left navigation menu, select .
Available integrations タブにアクセスするか、Deployed integrations タブで Add Integration を選択します。
インテグレーションフィルターメニューで、By Use Case を選択し、Monitor Infrastructure のユースケースを選択します。
Cloud Integrations セクションで、Google Cloud Platform タイルを選択し、Google Cloud Platform ガイド付きセットアップを開きます。
Complete the following fields:
Name. Type in the name of the GCP integration.
Project. Select Add Project, next select Import Service Account Key and import one or more of the JSON key files that you downloaded from GCP in Configure GCP.
Services. By default the new integration syncs with all supported GCP services. Select All services > Sync only selected services to select specific services to sync with.
Poll rate. Select the rate (in seconds) at which you want Splunk Observability Cloud to poll GCP for metric data, with 1 minute as the minimum unit, and 10 minutes as the maximum unit. For example, a value of 300 polls metrics once every 5 minutes.
Specify data to import: Metadata and/or metrics.
Specify if you want to use quota from the project where metrics are stored. See Use a single principal for your resources for more information.
Optional fields:
Custom Metric Type Domains. To list any additional GCP service domain names that you want to monitor, use commas to separate domain names in the Custom Metric Type Domains field. For example, to obtain Apigee metrics, add
apigee.googleapis.com.
For information on the available GCP metric domains refer to the official GCP docs at Google Cloud metrics .
カスタムメトリクスタイプドメインの構文については、Splunk 開発者ドキュメントの Custom metric type domain examples を参照してください。
Compute Metadata Included List. If you select Compute Engine as one of the services to monitor, you can enter a comma-separated list of Compute Engine Instance metadata keys to send as properties. These metadata keys are sent as properties named
gcp_metadata_<metadata-key>.
これでGCPとのインテグレーションは完了です。
注釈
Splunk はデータの可用性について責任を負わず、接続してからアカウントから有効なデータが表示されるようになるまで最大数分 (設定によってはそれ以上) かかることがあります。
Use a single principal for your resources 🔗
In IAM you can grant access to your resources to one or more entities called principals, regardless of the authentication method (single Service Account or Workload Identity Federation).
If you’re using a single principal for multiple projects, GCP tracks all API usage quota in the project where the principal originates from, which can result in throttling in your integration. To mitigate this, select Use quota from the project where metrics are stored. To use this option the principal provided for the project needs either the serviceusage.services.use permission or the Service Usage Consumer role.
For a more detailed description see Principals in GCP’s docs.
Alternatives to connect to GCP 🔗
Integrate GCP using the API 🔗
You can also integrate GCP with Splunk Observability Cloud using the GCP API.
See Integrate Google Cloud Platform Monitoring with Splunk Observability Cloud in our developer portal for details.
Connect to GCP using Terraform 🔗
Terraform を使って接続するには、Splunk Terraform を使ってクラウドサービスを接続する を参照してください。
次のステップ 🔗
セットアップを確認するには、セットアップページの最後にあるリストに表示されているGCPインテグレーションの詳細を調べます。
For details about the metrics provided by an GCP integration, see Google Cloud Monitoring metrics and metadata
To send logs from GCP to Splunk Observability Cloud, follow the instructions in GCP ログを Splunk プラットフォームに送信する
Learn about Splunk Observability Cloud’s GCP Infrastructure Monitoring options
To learn more about Splunk Observability Cloud’s data model, refer to Splunk Observability Cloud のデータ型