Skip to main content

​
Overview

The Google Cloud Platform (GCP) integration connects GCP projects to G360. Once configured, G360 securely accesses supported GCP services and collects cloud infrastructure, operational, and usage metrics for reporting and analysis. Using this integration, administrators can:
  • Create connections and authenticate with a Service Account
  • Enable individual GCP services as data scopes (Billing, Carbon, Recommender, Monitoring, Asset Inventory)
  • Monitor cloud usage and infrastructure metrics

​
Prerequisites

Before configuring the integration, ensure you have:
  • Access to G360
  • A Google Cloud Platform project
  • Permission to create Service Accounts in that project: the Editor or Owner role, or a custom role that includes iam.serviceAccounts.create and iam.serviceAccountKeys.create
  • Permission to enable APIs and assign IAM roles at the project level, and at the organization level if you plan to enable the Carbon or Governance scopes
If you don’t have Owner, Editor, or IAM Admin access on the GCP project, ask your organization’s GCP administrator to perform these steps or grant you the required access.

​
Open GCP Connections

1

Open Cloud Provider Metrics

In the Engineering Metrics Dashboard, go to Integration → Cloud Provider Metrics.
2

Open GCP Connections

Choose GCP Connections.
The page lists every configured GCP connection:

​
Prepare GCP credentials

G360 authenticates to your GCP project with a Service Account and a downloaded JSON key file. You need the project’s Project ID and the Service Account’s JSON key before you create a connection.
1

Find your Project ID

Sign in to the Google Cloud Console. Click the project selector dropdown next to the Google Cloud logo and find your project. You need the Project ID column, not the project name or number.Alternatively, with the project selected, check the Project Info card on the Cloud Console dashboard. Copy the Project ID exactly as shown. It is a lowercase string, for example my-app-prod-123456.
2

Create or reuse a Service Account

If your organization already has a dedicated Service Account for monitoring tools, reuse it and skip to the Generate the JSON key step.Otherwise, in the Cloud Console, go to IAM & Admin → Service Accounts and click + Create Service Account. Enter a name, for example engineering-metrics-monitoring, then click Create and Continue.
3

Grant IAM roles

Under Grant this service account access to project, assign the roles listed in Required APIs and IAM roles. You can also add them later from the Service Accounts page. Click Continue, then Done.
4

Generate the JSON key

Open the Service Account, select the Keys tab, click Add Key → Create new key, choose JSON, then click Create. The key file downloads automatically.
Google lets you download the private key only once, at creation time. If you lose it, create a new key from the Keys tab and delete the old, unused one.
5

Copy the credentials

Open the downloaded file in a text editor and copy its entire contents, including the opening and closing { }. You paste it into the connection’s Service Account Credentials (JSON) field.

​
Required APIs and IAM roles

The Service Account needs specific APIs enabled and IAM roles granted, depending on which data scopes you plan to use.
In the Cloud Console, go to APIs & Services → Library, search for the API by name (for example “Cloud Asset Inventory API”), then click Enable. Repeat for each API your scopes require.
Go to IAM & Admin → IAM, click + Grant Access, and enter the Service Account’s email under New principals (format: name@project-id.iam.gserviceaccount.com). Select the role, then click Save. Repeat for each required role.
Click the project selector, switch to the Organization tab, then go to IAM & Admin → IAM and grant access the same way as a project-level role.
If you don’t see an Organization option in the project selector, your account lacks access to the organization resource. Ask your GCP organization administrator to assign these roles instead.

​
Create a connection

1

Start a new connection

Click New Connection. The Manage Connections: GCP dialog opens.
2

Enter connection details

3

Set the Active toggle

Turn Active on to include the connection in scheduled and manual syncs.
4

Test the connection

Click Test Connection and wait for validation. If it fails, verify the Project ID and Service Account credentials.
5

Save the connection

Click Save Connection. The connection appears in the GCP Connections list.

​
Manage connections

Click the Edit icon under Actions, update the fields, then click Test Connection and Save Connection. Changes take effect immediately.
Submitting new credentials, or changing the Project ID, permanently deletes all previously synced data for this connection before it re-syncs under the new settings.
Click the Delete icon under Actions and confirm. This removes the integration for that project.
Deleting a connection immediately erases all previously collected data for it, not just future collection. If the connection is linked to a Project, unlink it first. Deletion is blocked otherwise.
Active connections collect metrics on an ongoing basis. Inactive connections stay configured but collect nothing until you enable them again.

​
Configure data scopes

A data scope controls which GCP service G360 collects data from. Select the connection, click Add Data Scope, then configure one of the scopes below.
Collects cloud spending, service usage costs, and project- or resource-level cost allocation.
Billing export is configured at the Cloud Billing account level and requires the Billing Account Administrator role.
  1. In BigQuery, select the destination project, then create a dataset (for example billing_export_dataset) in a multi-region location such as US or EU.
  2. Go to Billing → Cost management → Billing export and open the BigQuery export tab.
  3. Next to Standard usage cost (and Detailed usage cost for resource-level detail), click Edit settings and select the project and dataset you created.
The Billing Dataset is the dataset ID. Expand it in BigQuery to find the generated table, named gcp_billing_export_v1_<billing_account_id>. Combine the dataset and table name for the Billing Table value.
New export data can take up to 24 hours to appear. Historical backfill takes up to 5 days and covers only the current and previous month.

​
Synchronization and metrics

Once a connection is Active and has data scopes, G360 collects data for each scope in scheduled and manual syncs. Only enabled scopes are collected, and each scope needs its API and IAM roles. Billing and Carbon data depend on their BigQuery exports, so new data can lag behind the export delays noted in each scope.

​
Troubleshooting

Possible causes
  • Missing BigQuery roles
  • Billing Export not enabled
  • Wrong Dataset or Table value
Actions
  • Assign the BigQuery Job User and BigQuery Data Viewer roles.
  • Verify Billing Export is enabled.
  • Confirm the Dataset and Table values.
Possible causes
  • Required API not enabled
  • Wrong Target Project IDs
  • Missing IAM roles for the scope
Actions
  • Verify the required APIs are enabled.
  • Confirm the Target Project IDs are correct.
  • Confirm the Service Account has the scope’s required IAM roles.
Possible causes
  • Project name or number used instead of the Project ID
  • Incomplete or outdated JSON key
  • Required APIs not enabled
Actions
  • Re-copy the Project ID from the Cloud Console project selector (not the project name or number).
  • Re-open the downloaded JSON file and copy its full contents again.
  • Generate a new Service Account key if the original was deleted or lost.
  • Confirm the required APIs are enabled in APIs & Services → Library.

​
Best practices

  • Use a dedicated Service Account for the G360 integration.
  • Assign only the required IAM permissions.
  • Enable only the scopes you need.
  • Verify Billing Export tables before enabling the Billing or Carbon scopes.
  • Avoid sharing Service Account JSON credentials, and rotate Service Account keys periodically.

​
Summary

The GCP integration connects GCP projects to G360 to collect billing, carbon, recommendation, monitoring, and asset inventory data. Create a Service Account with the required APIs and roles, add a connection with its JSON key, then enable the data scopes you need.