After you populate your assets in Migration Center with an automatic scan or a manual upload, you can review the basic information about your infrastructure directly in Migration Center, both at the asset level, and globally. This lets you perform a first, very basic assessment of your infrastructure. You can also export your data to perform a more in-depth analysis.
Migration Center lets you view the details of the servers that you scan with the available collection methods. It also let you view the details of database deployments that you collect with the database scripts.
View details for an individual asset
To view the details about a specific asset, follow these steps:
In the Google Cloud console, go to the Assets page.
On the assets details page, click the Servers or Database deployments tab, depending on the type of asset that you want to view.
From the list of assets, click the asset for which you want to view information about.
On the individual asset page, you can see different information, depending on the asset being a server or a database deployment.
Available details for servers
On the details page for a server, you can see the basic information about the server, including the name, IP address, and operating system. You can also see the following tabs that provide you additional information about the server:
- Insights. This tab shows the Google Cloud products that you can migrate the server to, and the fit score of the match. For more information about insights, see View and understand insights.
- Details. This tab shows all the data that was collected about your server, including information about CPU, disks, network, and vCenter.
- Metadata. This tab provides you with additional information
about the server, such as:
- Contributing sources, which is the name of the discovery client or import job that created the asset.
- Full asset name
- Asset creation date
- Date of the last update
- Performance. This tab shows all the aggregated performance data and
statistics collected with the Migration Center discovery client,
manual file import, and the
mcdc
CLI, such as:- Daily input/output operations per second
- Daily memory usage
- Daily CPU usage
- Network bytes received and sent per second
Available details for databases
On the details page for a database, you can see the basic information about the database, including the name, engine, edition, and version. You can also see the following tabs that provide you additional information about the database deployment:
- Insights. This tab shows the Google Cloud products that you can migrate the database to, and the fit score of the match. For more information about insights, see View and understand insights. If you click the fit score, you can see the detailed fit assessment for the migration. For more information, see Detailed fit assessment.
- Details. This tab shows all the data that was collected about your database, including the name, CPU, memory, and storage for the server that hosts the database.
- Metadata. This tab shows you the following additional information
about the database:
- Contributing sources, which is the name of the discovery client or import job that created the asset.
- Full asset name.
- Asset creation date.
- Date of the last update.
- Performance. This tab shows all the aggregated performance data and
statistics collected with the database collection scripts, such as:
- Daily input/output operations per second
- Daily memory usage
- Daily CPU usage
- Databases. This tab shows the details about the databases collected in a particular instance, and the number of schemas, tables, and other database configuration details.
Out of scope assets
Migration Center lets you mark assets as out of scope. This is useful when the discovery client finds and collects data from assets that you don't plan to migrate, for example corporate desktop machines, or assets that you are going to decommission.
After you mark an asset as out of scope, the following happens:
- The asset is removed from the list of in scope assets.
- The asset is never included in the TCO reports and in the Summary page for assets.
- The asset is hidden from the groups that it was included in.
- Existing labels remain associated with the asset.
- Asset data continues to be updated.
If you decide to bring an asset back in scope later, the asset retains its metadata and group memberships, and you don't lose any information about the asset.
To mark one or more assets as out of scope, follow these steps:
In the Google Cloud console, go to the Assets page.
Select the assets that you want to mark as out of scope, then click Out of scope.
In the dialog that appears, enter the reason for marking the asset as out of scope. You can use this to filter out of scope assets later.
Click Confirm.
To view out of scope assets, click the Out of scope tab on the Assets page.
To put one or more assets back in scope, follow these steps:
- From the Out of scope tab on the Assets page, select the assets that you want to put back in scope, then click Put back in scope.
- In the dialog that appears, click Confirm.
View infrastructure details
To view aggregated information about your infrastructure, follow these steps:
In the Google Cloud console, go to the Overview page.
The Overview page displays a dashboard with high-level information about your infrastructure, including graphs about OS installed, memory, cores, and storage.
What's next
- Learn how to view and understand insights.