New Relic offers an integration for reporting your Google Cloud Storage data to New Relic. Learn how to connect this integration to infrastructure monitoring and about the metric data that New Relic reports for this integration.
Google Cloud Storage is a Google Cloud Platform service that you can use to serve website content, to store data for archival and disaster recovery, and to distribute data objects via direct download. With the Google Cloud Storage integration, you can access these features:
- View charts and information about the data you are storing and retrieving from Google Cloud Storage.
- Create custom queries and charts in from automatically captured data.
- Set alerts on your Google Cloud Storage data directly from the Integrations page.
To enable the integration follow standard procedures to connect your GCP service to New Relic.
New Relic queries your Google Cloud Storage services based on a polling interval of 5 minutes.
After connecting the integration to New Relic and waiting a few minutes, data will appear in the New Relic UI. To find and use integration data, including your dashboards and your alert settings, go to one.newrelic.com > Infrastructure > GCP > Google Cloud Storage.
To create custom dashboards for the integration, create queries for the
GcpStorageBucketSample event type with the provider value
The integration reports metric data for all values of
response_code: The response code of the requests.
method: The name of the API method called.
The metric data that New Relic receives from your Google Cloud Storage integration includes:
Delta count of API calls.
Delta count of bytes received over the network.
Delta count of bytes sent over the network.
After March 2022, we're discontinuing support for several capabilities, including inventory data for cloud integrations. For more details, including how you can easily prepare for this transition, see our Explorers Hub post.
Inventory data for Google Cloud Storage bucket objects includes the following properties:
Access control list for the bucket that lets you specify who has access to your data and to what extent.
The Cross-Origin Resource Sharing (CORS) configuration for the bucket.
Time when the bucket was created.
Default access control list configuration for the bucket's blobs.
HTTP 1.1 entity tag for the bucket.
The bucket's website index page. This behaves as the bucket's directory index where missing blobs are treated as potential directories.
Labels for the bucket, in key/value pairs. This is only available if the GCP project is linked to New Relic through a service account and extended inventory collection is enabled.
The generation of the metadata for the bucket.
The name of the bucket.
The custom object that will be returned when a requested resource is not found.
The owner of the bucket. A bucket is always owned by the project team owners group.
The name that you assigned to the project.
A project consists of a set of users, a set of APIs, and settings for those APIs.
If set to
The default storage class for a bucket, if you don't specify one for a new object. The storage class defines how Google Cloud Storage stores objects in the bucket and determines the SLA and storage cost. For more information, see storage classes.
The zone where the bucket is deployed.