You can monitor Cloud Extensions from the following:
Monitoring from Google Cloud's operations suite Logs
If enabled, Google Cloud's operations suite Logs provide a simple way to view the logs generated by your Cloud Extensions.
To display logs from your Cloud Extensions, follow the directions from
Google Cloud's operations suite Logs
and search for
Monitoring from vSphere
Monitoring performance and operational statistics
To monitor performance and operational statistics for the Cloud Extension, click your datacenter and then use the Monitor > Migrate for Google Compute Engine Service tab. You can review performance and usage stats aggregated across all VMs and Nodes associated with this Cloud Extension. You can also review the total number of VMs running in cloud, WAN usage, IOPS, I/O latency and throughput, as well as other efficiency metrics.
The following metrics are available for periods of 1 Hour,1 Day, 7 days, 30 days, or a custom range:
- IOPS: Total I/O operations per second generated by VMs in Google Cloud using this Cloud Extension (nodes A + B).
- IO Latency (ms): Average I/O latency for IO operations across all VMs in Google Cloud, using this Cloud Extension.
- Throughput (Bytes/sec): Total throughput across all VMs in Google Cloud, using this Cloud Extension (nodes A + B).
- WAN Usage (Bytes/sec): Total WAN throughput in each direction for the Cloud Extension, as reported by nodes A + B.
- Total #VMs in Cloud (running or stopped): Total VMs in Google Cloud, using this Cloud Extension.
- Datastore IO Offload %: Average I/O offload across node A and B. This is based on the ratio of I/O operations that were handled in cloud by nodes A and B, compared to the total I/O operations over the related vSphere Datastores on premises.
To monitor the current run state of the Cloud Extension, review the Migrate for Google Compute Engine Cloud Extension portlet on the Virtual Datacenter Summary page.
Cloud Extensions may be in any of the following states:
For a detailed explanation about availability of Cloud Extensions, see the Cloud Extensions overview.
Diagnosing impaired Cloud Extensions
Cloud Extensions often become impaired because components were not successfully deployed or because of system failures during operation. You can see these impairments in the list of health checks that failed.
After fixing the underlying causes, you can start a Cloud Extension repair operation. Repairing the Cloud Extension attempts to re-create the missing components and/or run relevant health checks. For more information, see Repairing a Cloud Extension. Once the Cloud Extension is repaired, its status becomes Active.
The following health checks are performed every minute to report on Cloud Extension status:
- Cache Store Accessibility
- Velostrata Storage Grid Service Status
- Velostrata Cloud Edge Service
- SCSI Target
- Cloud Edge Local Storage
- Cloud Edge Functionality
- Exporter Service
- Exporter Functionality
- On-Premises Edge Service
Viewing detailed Cloud Extension status from vCenter
- To view the Cloud Extension status, view the Datacenter > Summary tab.
- Click the information icon in the status column for an Impaired Cloud Extension. The pop-up window displays component statuses as well as when the Cloud Extension was last Active.
- When the Cloud Extension status becomes Impaired, an alarm is triggered in the Summary tab.
- To view more details on an alarm, click to select the alarm.
- To acknowledge the alarm, click Acknowledge.
- To view the related events, select Monitor > Events.
Viewing Cloud Extension status from Migrate for Compute Engine Manager
The Migrate for Compute Engine Manager provides basic status information on your Cloud Extensions.
- Sign in to your Migrate for Compute Engine Manager.
- Click the Target Cloud icon.
- A list of Cloud Extensions appears with the state of each listed on the far right.
- You can perform limited operations on a Cloud Extension by selecting one and using the buttons at the top to start, stop, delete, or repair.