> ## Documentation Index
> Fetch the complete documentation index at: https://docs.heygarth.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Gcp

## Overview

The Google Cloud Platform (GCP) integration allows administrators to connect GCP projects to Engineering Metrics. Once configured, Engineering Metrics can securely access supported GCP services and collect cloud infrastructure, operational, and usage metrics for reporting and analysis.

Using this integration, users can:

* Create GCP connections
* Authenticate using GCP Service Account credentials
* Configure GCP data collection scopes
* Enable or disable individual GCP services
* Associate cloud resources with projects
* Monitor cloud usage and infrastructure metrics

## Prerequisites

Before configuring the integration, ensure you have:

* Access to the Engineering Metrics Dashboard
* A Google Cloud Platform project
* A GCP Service Account with appropriate permissions
* Service Account JSON credentials
* Permissions to configure integrations within Engineering Metrics

## Navigate to GCP Connections

1. Open the Engineering Metrics Dashboard.
2. Navigate to **Integration**.
3. Select **Cloud Provider Metrics**.
4. Choose **GCP Connections**.

The GCP Connections page displays all configured GCP integrations.

## Create a New GCP Connection

1. Click **New Connection**.
2. The **Manage Connections: GCP** window will appear.

## Configure Connection Details

### Connection Name

Enter a unique name for the GCP connection.

Examples:

* GCP Production
* Engineering Platform
* Analytics Environment
* Internal Cloud Resources

### Project ID

Enter the Google Cloud Project ID that will be connected.

Example:

```text theme={null}
my-gcp-project-123456
```

The Project ID identifies the GCP project from which metrics and resources will be collected.

### Service Account Credentials (JSON)

Paste the Service Account JSON credentials into the provided field.

The credentials are used by Engineering Metrics to authenticate with Google Cloud services.

Example:

```json theme={null}
{
  "type": "service_account",
  "project_id": "my-project",
  ...
}
```

<Note>
  The Service Account must have sufficient permissions to access the services and resources that will be monitored.
</Note>

### Active

Enable the **Active** toggle to make the connection available for data collection and synchronization.

## Test the Connection

Before saving the connection:

1. Click **Test Connection**.
2. Wait for the validation process to complete.

### Expected Result

* If the configuration is valid, the connection test will succeed.
* If validation fails, verify the Project ID and Service Account credentials before retrying.

## Save the Connection

1. After successful validation, click **Save Connection**.
2. The connection will appear in the Connections list.

## Configure Data Scopes

After creating the connection:

1. Select the GCP connection.
2. Click **Add Data Scope**.

A data scope defines which GCP services and resources Engineering Metrics will monitor.

## Understanding GCP Scopes

The Configure GCP Scopes window allows administrators to enable or disable supported Google Cloud services individually.

Each enabled scope controls the collection of metrics and resource information from a specific GCP service.

## Billing Scope

The Billing scope collects billing and cost-related information from Google Cloud.

Collected information may include:

* Billing accounts
* Cost allocation data
* Cloud spending information
* Service consumption costs

## Carbon Scope

The Carbon scope collects cloud carbon footprint information.

Collected information may include:

* Carbon emissions metrics
* Environmental impact reporting
* Sustainability data

## Recommender Scope

The Recommender scope collects optimization recommendations generated by Google Cloud.

Collected information may include:

* Resource optimization recommendations
* Cost-saving opportunities
* Performance improvement suggestions

## Monitoring Scope

The Monitoring scope collects operational monitoring information.

Collected information may include:

* Resource health metrics
* Monitoring data
* Service performance information
* Infrastructure activity metrics

## Asset Inventory Scope

The Asset Inventory scope collects information about cloud resources within the connected project.

Collected information may include:

* Compute resources
* Storage resources
* Networking components
* Cloud service inventories

## Scope Configuration

Each enabled scope may require additional configuration values.

Depending on the selected scope, administrators may be required to provide:

* Scope Name
* Dataset Name
* Project Information
* Resource Identifiers
* Tagging Configuration

These values determine how Engineering Metrics retrieves and organizes cloud data.

## Managing Data Scopes

Users can:

* Add Data Scope
* Associate Scope Config
* Delete Data Scope

These options allow administrators to control which cloud resources and services are monitored.

## Understanding Scope Associations

Scope associations define how collected GCP data is mapped within Engineering Metrics.

This configuration enables reporting, dashboards, and project-level analytics to use collected cloud information.

## Monitoring GCP Data Collection

Once the connection and scopes are configured, Engineering Metrics begins collecting data from the enabled GCP services.

Collected information becomes available for:

* Cloud dashboards
* Infrastructure reporting
* Resource analytics
* Operational insights
* Sustainability reporting
* Cost management analysis

## Troubleshooting

### Connection Test Failed

Possible causes:

* Invalid Project ID
* Invalid Service Account JSON
* Missing permissions
* Network connectivity issues

Recommended actions:

* Verify the Project ID
* Validate the Service Account credentials
* Confirm service account permissions
* Retry the connection test

### Data Not Appearing

Possible causes:

* Required scopes are disabled
* Service permissions are missing
* Synchronization is still in progress

Recommended actions:

* Verify scope configuration
* Confirm service account access
* Allow additional time for data collection

### Scope Configuration Errors

Possible causes:

* Missing required scope fields
* Invalid dataset configuration
* Incorrect project information

Recommended actions:

* Review scope settings
* Verify all required values
* Save the configuration again

## Best Practices

* Use dedicated Service Accounts for integrations
* Assign only required permissions
* Use descriptive connection names
* Enable only required scopes
* Regularly review scope configurations
* Monitor cloud resource reporting for accuracy

## Summary

The GCP integration enables Engineering Metrics to securely connect with Google Cloud Platform projects and collect cloud infrastructure, operational, sustainability, and cost-related information. By configuring connections and enabling appropriate scopes, organizations can gain visibility into cloud usage, performance, optimization opportunities, and resource management across their Google Cloud environments.