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.
Activate integration
To enable the integration, follow the 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 > All capabilities > Infrastructure > GCP and select an integration.
Data is attached to the following event types:
Entity | Event Type | Provider |
---|---|---|
Endpoint |
|
|
Feature store |
|
|
Feature Online Store |
|
|
Location |
|
|
Index |
|
|
PipelineJob |
|
|
For more on how to use your data, see Understand and use integration data.
Metric data
This integration collects GCP data for VertexAI.
VertexAI Endpoint data
Metric | Unit | Description |
---|---|---|
| Percent | Average fraction of time over the past sample period during which the accelerator(s) were actively processing. |
| Bytes | Amount of accelerator memory allocated by the deployed model replica. |
| Count | Number of online prediction errors. |
| Bytes | Amount of memory allocated by the deployed model replica and currently in use. |
| Bytes | Number of bytes received over the network by the deployed model replica. |
| Bytes | Number of bytes sent over the network by the deployed model replica. |
| Count | Number of online predictions. |
| Milliseconds | Online prediction latency of the deployed model. |
| Milliseconds | Online prediction latency of the private deployed model. |
| Count | Number of active replicas used by the deployed model. |
| Count | Number of different online prediction response codes. |
| Count | Target number of active replicas needed for the deployed model. |
VertexAI Featurestore data
Metric | Unit | Description |
---|---|---|
| Percent | The average CPU load for a node in the Featurestore online storage. |
| Percent | The CPU load for the hottest node in the Featurestore online storage. |
| Count | The number of nodes for the Featurestore online storage. |
| Count | Number of entities updated on the Featurestore online storage. |
| Milliseconds | Online serving latencies by EntityType. |
| Bytes | Request size by EntityType. |
| Count | Featurestore online serving count by EntityType. |
| Bytes | Response size by EntityType. |
| Bytes | Number of bytes billed for offline data processed. |
| Bytes | Bytes stored in Featurestore. |
| Count | Number of streaming write requests processed for offline storage. |
| Seconds | Time (in second) since the write API is called until it is written to offline storage. |
VertexAI FeatureOnlineStore data
Metric | Unit | Description |
---|---|---|
| Count | Number of serving count by FeatureView. |
| Bytes | Serving response size by FeatureView. |
| Milliseconds | Online serving latencies by FeatureView. |
| Milliseconds | Number of running syncs at given point of time. |
| Seconds | Measure of the serving data age in seconds. |
| Count | Breakdown of data in Feature Online Store by synced timestamp. |
| Percent | The average CPU load of nodes in the Feature Online Store. |
| Percent | The CPU load of the hottest node in the Feature Online Store. |
| Count | The number of nodes for the Feature Online Store(Bigtable). |
| Count | Bytes stored in the Feature Online Store. |
VertexAI Location data
Metric | Unit | Description |
---|---|---|
| Count | Number of requests per base model. |
| Count | Number of attempts to exceed the limit on quota metric. |
| Count | Current limit on quota metric. |
| Count | Current usage on quota metric. |
| Count | Number of pipeline jobs being executed. |
| Count | Number of pipeline tasks being executed. |
VertexAI Index data
Metric | Unit | Description |
---|---|---|
| Count | Number of successfully upserted or removed datapoints. |
| Milliseconds | The latencies between the user receives a UpsertDatapointsResponse or RemoveDatapointsResponse and that update takes effect. |
| Count | Number of stream update requests. |
VertexAI Pipeline Job data
Metric | Unit | Description |
---|---|---|
| Seconds | Runtime seconds of the pipeline job being executed (from creation to end). |
| Count | Total number of completed Pipeline Tasks. |