---
title: Troubleshooting GCP integrations
source: https://docs.newrelic.com/docs/infrastructure/google-cloud-platform-integrations/troubleshooting/troubleshooting-gcp-integrations
---

This page covers common issues with New Relic's Google Cloud Platform (GCP) integrations and how to resolve them.

## No data appearing after setup [#no-data]

### Check the basics [#no-data-basics]

-   Wait 5 minutes after completing setup. Data takes a few minutes to arrive.
-   Confirm you selected at least one service during setup.
-   Check that the **Stackdriver Monitoring API** is enabled in your GCP project.

### Workload Identity Federation integration [#no-data-wif]

If you connected with [Workload Identity Federation (WIF)](https://docs.newrelic.com/docs/infrastructure/google-cloud-platform-integrations/get-started/install-and-configure/connect-gcp-workload-identity-federation):

-   Verify all five [required APIs](https://docs.newrelic.com/docs/infrastructure/google-cloud-platform-integrations/get-started/install-and-configure/connect-gcp-workload-identity-federation#step-2) are enabled.
-   Confirm the service account has the **Viewer** and **Service Usage Consumer** roles.
-   Check that the **Workload Identity User** role is granted to the pool principal on your service account.

### Service account integration [#no-data-sa]

If you connected with a [New Relic service account](https://docs.newrelic.com/docs/infrastructure/google-cloud-platform-integrations/get-started/install-and-configure/connect-gcp-service-account):

-   Verify the New Relic service account ID appears in your project's IAM.
-   Confirm it has the **Viewer** and **Service Usage Consumer** roles.
-   If using [domain restriction constraints](https://docs.newrelic.com/docs/infrastructure/google-cloud-platform-integrations/get-started/install-and-configure/connect-gcp-service-account#reqs), ensure New Relic is allowed.

## Authentication errors [#auth-errors]

### Reauthorize New Relic [#reauthorize]

If you see API authentication errors when you [integrate your Google Cloud Platform (GCP) services](https://docs.newrelic.com/docs/introduction-google-cloud-platform-integrations) with New Relic, reauthorize New Relic to use your GCP APIs:

1.  Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Infrastructure > GCP**.
2.  From your GCP account page, select **Reauthorize New Relic**.
3.  Follow standard procedures to [connect your GCP services to New Relic](https://docs.newrelic.com/docs/infrastructure/google-cloud-platform-integrations/get-started/connect-google-cloud-platform-services-new-relic).

If reauthorizing doesn't resolve the errors, you can unlink the integration and connect again. See the unlink steps in your [connection guide](https://docs.newrelic.com/docs/infrastructure/google-cloud-platform-integrations/get-started/connect-google-cloud-platform-services-new-relic).

Common reasons for these errors include:

-   A user manually revoked New Relic's authorization to use GCP APIs from the Google account management application.
-   The authorization for New Relic to use GCP APIs does not include one or more of the permissions ([Google OAuth scopes](https://developers.google.com/identity/protocols/googlescopes)) needed to query one or more of the GCP APIs.
-   The authorization for New Relic to use GCP APIs has expired.

### WIF authentication errors [#wif-auth]

These errors are specific to [Workload Identity Federation](https://docs.newrelic.com/docs/infrastructure/google-cloud-platform-integrations/get-started/install-and-configure/connect-gcp-workload-identity-federation) connections.

| **Error**                                            | **How to resolve it**                                                                                                                                                                                                                                                                     |
| ---------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Token audience mismatch`                            | Your WIF provider's allowed audience doesn't match what New Relic sends. When creating the OIDC provider, make sure you used the **Audience URL** shown in the New Relic setup UI.                                                                                                        |
| `Attribute condition not met`                        | The attribute condition on your WIF provider doesn't match the token New Relic sends. Check that: - The condition uses `assertion.nr_account_id == "YOUR_ACCOUNT_ID"` with the correct New Relic account ID. - You haven't added extra conditions that conflict with the token claims.    |
| `Permission denied` on service account impersonation | The pool principal doesn't have permission to impersonate your service account. Verify that: - You granted the `roles/iam.workloadIdentityUser` role on the service account. - The member matches the exact principal from your identity pool with the correct `nr_account_id` attribute. |
| `Service account not found`                          | The service account specified in the uploaded JSON config doesn't exist or no longer exists. Create it again or update the configuration.                                                                                                                                                 |

## Missing metrics for a specific service [#missing-metrics]

-   Confirm the service is enabled in **Infrastructure > GCP > Manage services**.
-   Check that the GCP service itself is active and generating metrics. Some services only report metrics when in use.
-   If using a [custom IAM role](https://docs.newrelic.com/docs/integrations/google-cloud-platform-integrations/get-started/integrations-custom-roles), verify you have the service-specific permissions for that service.

## Stale or delayed metrics [#stale-metrics]

-   Check the GCP Cloud Monitoring API quotas in your GCP project. If you're hitting rate limits, data collection can slow down. To request a higher quota:

    1.  In the Google Cloud console, go to **IAM & Admin > Quotas & System Limits**.
    2.  Filter by **Service: Cloud Monitoring API**.
    3.  Find the quota named **Time series queries per minute**, select it, and click **Edit Quotas** to request an increase.
-   For WIF integrations, verify the service account's token hasn't been revoked.
-   Check the account status dashboard in **Infrastructure > GCP** for any reported errors.

## GCP projects not visible during setup [#no-projects]

-   The authenticated account needs the `resourcemanager.projects.get` permission to list projects.
-   Alternatively, use the NerdGraph API to link projects by ID without needing to list them.

## Get more help [#get-help]

If none of the above resolves your issue, contact New Relic Support with:

-   Your New Relic account ID.
-   The GCP project ID.
-   Which connection method you used (WIF or service account).
-   Any error messages you see in the UI.