There are two types of operations that are useful for understanding the status and performance of your Migrate for Compute Engine environment:
A. Monitoring, which collects metrics, events, and metadata.
B. Logging, which collects log events.
Both of these are described below.
Monitoring Migrate for Compute Engine components
Migrate for Compute Engine's components, such as Cloud Extensions and the Migrate for Compute Engine Backend, provide metrics and alarms in Google Cloud's operations suite or vCenter. For more information, see the following topics:
- Using Google Cloud's operations suite Monitoring
- Viewing Google Cloud's operations suite Logs
- Monitoring the Cloud Extension
- Alarms and events
- Checking the backend registration
- Health checks
Monitoring migrated VMs
Migrate for Compute Engine allows you to monitor performance of VMs migrated to Google Cloud. This includes:
- Graphs of migration performance (such as storage throughput and operation times) in Stackdriver Monitoring.
- Alarms and events on the vSphere web client.
- Monitoring VMs on Compute Engine.
Additionally, you can check the status of an individual VM by viewing its console log on either vSphere or the Migrate for Compute Engine Manager.
Because your workloads run on Google Cloud, you have additional logging and monitoring features available, including:
- Compute Engine audit logs and usage logs
- VPC flow logs for debugging network traffic
About Google Cloud's operations suite
Disabling Google Cloud's operations suite Monitoring
You can disable the Google Cloud's operations suite Monitoring and Logs in the Migrate for Compute Engine Manager. See Disabling Google Cloud's operations suite Monitoring.