This page covers common issues with New Relic's Google Cloud Platform (GCP) integrations and how to resolve them.
No data appearing after setup
Check the 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
If you connected with Workload Identity Federation (WIF):
- Verify all five required APIs 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
If you connected with a New Relic 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, ensure New Relic is allowed.
Authentication errors
Reauthorize New Relic
If you see API authentication errors when you integrate your Google Cloud Platform (GCP) services with New Relic, reauthorize New Relic to use your GCP APIs:
- Go to one.newrelic.com > All capabilities > Infrastructure > GCP.
- From your GCP account page, select Reauthorize New Relic.
- Follow standard procedures to connect your GCP services to 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.
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) needed to query one or more of the GCP APIs.
- The authorization for New Relic to use GCP APIs has expired.
WIF authentication errors
These errors are specific to Workload Identity Federation connections.
Error | How to resolve it |
|---|---|
| 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. |
| The attribute condition on your WIF provider doesn't match the token New Relic sends. Check that:
|
| The pool principal doesn't have permission to impersonate your service account. Verify that:
|
| 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
- 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, verify you have the service-specific permissions for that service.
Stale or delayed metrics
- Check the GCP Cloud Monitoring API quotas in your GCP project. If you're hitting rate limits, data collection can slow down.
- 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
- The authenticated account needs the
resourcemanager.projects.getpermission to list projects. - Alternatively, use the NerdGraph API to link projects by ID without needing to list them.
Get more 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.