New Relic's integrations include an integration for reporting your GCP Run data to our products. Here we explain how to activate the integration and what data it collects.
To enable the integration follow standard procedures to connect your GCP service to New Relic.
Configuration and polling
You can change the polling frequency and filter data using configuration options.
Default polling information for the GCP Run integration:
- New Relic polling interval: 5 minutes
Find and use data
To find your integration data, go to one.newrelic.com > Infrastructure > GCP and select an integration.
Data is attached to the following event type:
For more on how to use your data, see Understand and use integration data.
This integration collects GCP Run data for Revision.
Run Revision data
||Seconds||Billable time aggregated from all container instances of the revision. For a given container instance, billable time occurs when the container instance is starting or at least one request is being processed. Billable time is rounded up to the nearest 100 milliseconds. Examples: If a revision with 2 container instances has been continuously serving traffic in the last minute, the value is 2s/s with the default "rate" aligner. If a single request lasting 30ms was received by a revision in the past minute, it is rounded up to 100ms and averaged to 1.7ms/s over the minute with the default "rate" aligner.|
||Seconds||Container CPU allocation of the revision in seconds.|
||Other||Container memory allocation of the revision in Gigabytes-seconds.|
||Count||Number of requests reaching the revision. Excludes requests that are not reaching your container instances (e.g. unauthorized requests or when maximum number of instances is reached).|
||Milliseconds||Distribution of request latency in milliseconds reaching the revision.|