GCP Compute Engine Instance

A Google Cloud Platform (GCP) Compute Engine instance is a virtual machine hosted on Google's infrastructure.

You must configure cloud connections to monitor this entity. See Configure Google Cloud Platform Connection.

Cisco Cloud Observability displays GCP entities on the Observe page. Metrics are displayed for specific entity instances in the list and detail views.

This document contains references to third-party documentation. Splunk AppDynamics does not own any rights and assumes no responsibility for the accuracy or completeness of such third-party documentation.

Detail View

To display the detail view of a Compute Engine instance:

Navigate to the Observe page.
Under Compute, click Hosts.
The Hosts list view now displays. Click the GCP tab.
From the list, click a Compute Engine instance Name to display the detail view.
The detail view displays metrics, key performance indicators, and properties (attributes) related to the instance you selected.
(Optional) If you have set up Host Monitoring, you can use the Data Source dropdown to choose a data source for your metrics. Selecting All Sources from the dropdown displays metrics from the GCP Compute Engine instance and Cisco AppDynamics Hosts for GCP. To display metrics from one source, select the host from the dropdown.

Metrics and Key Performance Indicators

Cisco Cloud Observability displays the following metrics and key performance indicators (KPIs) for GCP Compute Engine. See Google Cloud metrics.

Display Name	Source Metric	Description
CPU Utilization (%)	`instance/cpu/utilization`	Fractional utilization of allocated CPU on this instance. Values are typically numbers between 0.0 and 1.0 (but some machine types allow bursting above 1.0). Charts display the values as a percentage between 0% and 100% (or more). This metric is reported by the hypervisor for the VM and can differ from `agent.googleapis.com/cpu/utilization`, which is reported from inside the VM. Sampled every 60 seconds. After sampling, data is not visible for up to 240 seconds.
Reserved Cores (vCPUs)	`instance/cpu/reserved_cores`	Number of vCPUs reserved on the host of the instance. Sampled every 60 seconds. After sampling, data is not visible for up to 240 seconds.
CPU Usage Time (s)	`instance/cpu/usage_time`	Delta vCPU usage for all vCPUs, in vCPU-seconds. To compute the per-vCPU utilization fraction, divide this value by (end-start)*N, where end and start define this value's time interval and N is `compute.googleapis.com/instance/cpu/reserved_cores` at the end of the interval. This value is reported by the hypervisor for the VM and can differ from `agent.googleapis.com/cpu/usage_time`, which is reported from inside the VM. Sampled every 60 seconds. After sampling, data is not visible for up to 240 seconds.
Scheduler Wait Time (s)	`instance/cpu/scheduler_wait_time`	Wait time is the time a vCPU is ready to run, but unexpectedly not scheduled to run. The wait time returned here is the accumulated value for all vCPUs. The time interval for which the value was measured is returned by Monitoring in whole seconds as start_time and end_time. This metric is only available for VMs that belong to the e2 family or to overcommitted VMs on sole-tenant nodes. Sampled every 60 seconds. After sampling, data is not visible for up to 240 seconds.
Network Throughput (By) Received Bytes Sent Bytes Mirrored Throughput (By)	`instance/network/received_bytes_count`	Count of bytes received from the network. Sampled every 60 seconds. After sampling, data is not visible for up to 240 seconds.
	`instance/network/sent_bytes_count`	Count of bytes sent over the network. Sampled every 60 seconds. After sampling, data is not visible for up to 240 seconds.
	`mirroring/mirrored_bytes_count`	Count of mirrored bytes. Sampled every 60 seconds. After sampling, data is not visible for up to 240 seconds.
Network Packets (Count/Sec) Received Packets Sent Packets Dropped Packets	`instance/network/received_packets_count`	Count of packets received from the network. Sampled every 60 seconds. After sampling, data is not visible for up to 240 seconds.
	`instance/network/sent_packets_count`	Count of packets sent over the network. Sampled every 60 seconds. After sampling, data is not visible for up to 240 seconds.
	`mirroring/dropped_packets_count`	Count of dropped mirrored packets. Sampled every 60 seconds. After sampling, data is not visible for up to 240 seconds.
Allocated Ports (Count)	`nat/allocated_ports`	Number of ports allocated to a VM by the NAT gateway. Sampled every 60 seconds. After sampling, data is not visible for up to 165 seconds.
Closed/New Connections (Count)	`nat/closed_connections_count`	Count of connections closed over the NAT gateway. Sampled every 60 seconds. After sampling, data is not visible for up to 165 seconds.
Closed/New Connections (Count)	`nat/new_connections_count`	Count of new connections created over the NAT gateway. Sampled every 60 seconds. After sampling, data is not visible for up to 165 seconds.
Open Connections (Count)	`nat/open_connections`	Number of connections currently open on the NAT gateway. Sampled every 60 seconds. After sampling, data is not visible for up to 165 seconds.
Disk Used (By)	`guest/disk/bytes_used`	Number of bytes used on disk for file systems. For Container-Optimized OS, or Ubuntu running GKE.
Disk I/O Duration (ms)	`guest/disk/io_time`	The cumulative time spent on the I/O operations that are in progress; that is, the actual time in queue and when disks were busy. Requests issued in parallel are counted as a single one. For Container-Optimized OS, or Ubuntu running GKE. Sampled every 60 seconds.
Disk Operation Duration (ms)	`guest/disk/operation_time`	Amount of time spent on the disk operations, by direction. This metric only includes time spent on completed operations. For Container-Optimized OS, or Ubuntu running GKE.
Disk Operations (Count) Calin - For this metric, we are only using operation_count	`guest/disk/operation_count`	Disk operations count. For Container-Optimized OS, or Ubuntu running GKE.
	`guest/disk/merged_operation_count`	Merged disk operations count. Disk operations which are adjacent to each other may be merged by the kernel for efficiency. For Container-Optimized OS, or Ubuntu running GKE.
	`pending_operations`
Disk Weighted I/O Duration (ms)	`guest/disk/weighted_io_time`	The cumulative weighted IO time spent on the disk. For Container-Optimized OS, or Ubuntu running GKE. Sampled every 60 seconds

Properties (Attributes)

Cisco Cloud Observability displays the following properties for GCP Compute Engine.

Display Name	Property Name	Description
Cloud Provider	`cloud.provider`	The name of the cloud provider.
Account ID	`cloud.account.id`	The cloud account ID the resource is assigned to.
Region	`cloud.region`	The geographical region where the resource is running.
Availability Zone	`cloud.availability_zone`	The zone where the instance resides.
Platform	`cloud.platform`	The cloud platform in use.
ID	`host.id`	The unique identifier for the instance.
Name	`host.name`	The name of the instance.
Status	`cloud.host.state.name`	The status of the instance. Possible values: `PROVISIONING`, `STAGING`, `RUNNING`, `STOPPING`, `SUSPENDING`, `SUSPENDED`, `REPAIRING`, and `TERMINATED`
Launch Time	`cloud.host.launch_time`	The date and time the instance was created.
Disk Type	`cloud.host.root_device_volume.type`	The type of disk attached to this instance. Possible values: `SCRATH`, `PERSISTENT` (default)
Architecture	`host.arch`	The architecture of the boot disk. This value can be `arm64` or `x86_64`.
Disk IDs	`cloud.disk.ids`	The names of the attached disks.
Type	`cloud.host.type`	The machine type resource used for the instance.
Public IP Addresses	`cloud.host.public_ip_addresses`	An external IP address associated with the instance. Applies to `accessConfigs` (IPv4) only.
Private DNS Names	`cloud.host.private_dns_names`	The DNS domain name for the public PTR record.

Retention and Purge Time-To-Live (TTL)

For all cloud and infrastructure entities, the retention TTL is 180 minutes (3 hours) and the purge TTL is 525,600 minutes (365 days).

Third party names, logos, marks, and general references used in these materials are the property of their respective owners or their affiliates in the United States and/or other countries. Inclusion of such references are for informational purposes only and are not intended to promote or otherwise suggest a relationship between Splunk AppDynamics and the third party.