New Relic's integration with Google Kubernetes Engine (GKE) reports data about clusters hosted on Google's infrastructure. You can monitor and alert on your GKE instances data from our infrastructure UI, and you can create custom queries and chart dashboards.
Activate integration
To enable the integration:
- Make sure you have installed the infrastructure agent before activating GCP integrations from New Relic.
- 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 interval for the Google Kubernetes Engine integration is 5 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
The data New Relic receives from your Google Kubernetes Engine integration includes the following metric data. For more on these metrics, see Google's documentation on Metrics for Kubernetes Engine.
GcpKubernetesContainerSample
New Relic receives the following data from your GCP Kubernetes Engine integration and it is reported to a GcpKubernetesContainerSample
event type with the provider value GcpKubernetesContainer
. The container/accelerator
metrics are only available the experimental mode on kubernetes is enabled, and gpu has been added to your cluster and container. Query GcpKubernetesContainerSample
events to view data for the following attributes:
Name | Description |
---|---|
| Percent of time over the past sample period (10 seconds) during which the accelerator was actively processing. The |
| Total accelerator memory in bytes. The |
| Total accelerator memory allocated in bytes. The |
| CPU cores limit of the container. Sampled every 60 seconds. |
| Cumulative CPU usage on all cores in seconds. This number divided by the elapsed time represents usage as a number of cores, regardless of any core limit that might be set. |
| The fraction of the memory limit that is currently in use on the instance. This value cannot exceed 1 as usage cannot exceed the limit. Sampled every 60 seconds. After sampling, data is not visible for up to 60 seconds. This metric is available only when a maximum memory limit has been specified for the container. |
| Number of CPU cores requested by the container. Sampled every 60 seconds. |
| The fraction of the requested CPU that is currently in use on the instance. This value can be greater than 1 as usage can exceed the request. Sampled every 60 seconds. After sampling, data is not visible for up to 180 seconds. |
| Memory limit of the container in bytes. Sampled every 60 seconds. |
| The fraction of the memory limit that is currently in use on the instance. This value cannot exceed 1 as usage cannot exceed the limit. Sampled every 60 seconds. After sampling, data is not visible for up to 60 seconds. |
| Memory request of the container in bytes. Sampled every 60 seconds. |
| The fraction of the requested memory that is currently in use on the instance. This value can be greater than 1 as usage can exceed the request. Sampled every 60 seconds. After sampling, data is not visible for up to 60 seconds. |
| Memory usage in bytes. Sampled every 60 seconds. |
| Number of times the container has restarted. Sampled every 60 seconds. |
| Time in seconds that the container has been running. Sampled every 60 seconds. |
GcpKubernetesNodeSample
New Relic receives the following data from your GCP Kubernetes Engine integration and it is reported to a GcpKubernetesNodeSample
event type with the provider value GcpKubernetesNode
. Query GcpKubernetesNodeSample
events to view data for the following attributes:
Name | Description |
---|---|
| Number of allocatable CPU cores on the node. Sampled every 60 seconds. |
| The fraction of the allocatable CPU that is currently in use on the instance. This value cannot exceed 1 as usage cannot exceed allocatable CPU cores. Sampled every 60 seconds. After sampling, data is not visible for up to 180 seconds. |
| Cumulative CPU usage on all cores used on the node in seconds. Sampled every 60 seconds. |
| Total number of CPU cores on the node. Sampled every 60 seconds. |
| Cumulative memory bytes used by the node. Sampled every 60 seconds. |
| The fraction of the allocatable memory that is currently in use on the instance. This value cannot exceed 1 as usage cannot exceed allocatable memory bytes. Sampled every 60 seconds. After sampling, data is not visible for up to 60 seconds. |
| Number of bytes of memory allocatable on the node. Sampled every 60 seconds. |
| Cumulative memory bytes used by the node. Sampled every 60 seconds. |
| Cumulative number of bytes received by the node over the network. Sampled every 60 seconds. |
| Cumulative number of bytes transmitted by the node over the network. Sampled every 60 seconds. |
| Cumulative CPU usage on all cores used by the node level system daemon in seconds. Sampled every 60 seconds. |
| Memory usage by the system daemon in bytes. Sampled every 60 seconds. |
GcpKubernetesPodSample
New Relic receives the following data from your GCP Kubernetes Engine integration and it is reported to a GcpKubernetesPodSample
event type with the provider value GcpKubernetesPod
. Query GcpKubernetesPodSample
events to view data for the following attributes:
Name | Description |
---|---|
| Cumulative number of bytes received by the pod over the network. Sampled every 60 seconds. |
| Cumulative number of bytes transmitted by the pod over the network. Sampled every 60 seconds. |
| Total number of disk bytes available to the pod. Sampled every 60 seconds. |
| Number of disk bytes used by the pod. Sampled every 60 seconds. |
| The fraction of the volume that is currently being used by the instance. This value cannot be greater than 1 as usage cannot exceed the total available volume space. Sampled every 60 seconds. After sampling, data is not visible for up to 60 seconds. |