• English日本語한국어
  • Log inStart now

Google Cloud Spanner monitoring integration

New Relic's integrations with the Google Cloud Platform (GCP) include an integration to report Google Cloud Spanner data to New Relic. This document explains how to activate the GCP Cloud Spanner integration and describes the data that can be reported.


Google Cloud Spanner service is a globally-distributed relational database service built for the cloud. Using the Google Spanner Console, developers can create a Cloud Spanner instance, add schemas, write and modify data, and run queries.

Activate integration

To enable the integration follow standard procedures to connect your GCP service to New Relic.

Polling frequency

New Relic integrations query your GCP services according to a polling interval, which varies depending on the integration. The polling frequency for Google Cloud Spanner is five minutes. The resolution is 1 data point every minute.

Find and use data

After activating the integration and waiting a few minutes (based on the polling frequency), data will appear in the New Relic UI. To find and use your data, including links to your and alert settings, go to one.newrelic.com > All capabilities > Infrastructure > GCP > (select an integration).

Metric data

To view metric data for your GCP Spanner integration in New Relic, create NRQL queries for GcpSpannerInstanceSample and GcpSpannerDatabaseSample events and their related attributes.


Query GcpSpannerInstanceSample events in New Relic to view data for the following attributes:




Utilization of the provisioned CPU, between 0 and 1.


Utilization of the provisioned CPU by priority, between 0 and 1.


24-hour smoothed utilization of the provisioned CPU , between 0 and 1.


Total number of nodes.


Number of sessions in use.


Storage used in bytes.


Query GcpSpannerDatabaseSample events in New Relic to view data for the following attributes:




Uncompressed request bytes received by Cloud Spanner.


Rate of Cloud Spanner API requests.


Distribution of server request latencies for a database. This includes latency of request processing in Cloud Spanner backends and API layer. It does not include network or reverse-proxy overhead between clients and servers.


Uncompressed response bytes sent by Cloud Spanner.

Copyright © 2023 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.