Centralised self-hosted logging enables the automatic transmission of migration trace files, service logs, and configurations directly to a Google Cloud Storage bucket or an Azure Storage bucket, eliminating the need to store them on secondary servers.
While this feature is enabled at the service level, you can also choose to disable it for specific migration batches if required, providing flexibility in how logging is managed.
This document provides a step-by-step guide to enabling this feature and explains its functionality in detail.
Prerequisites
- Microsoft
- Google
Enable Centralised Self-Hosted logging
To enable centralised logging, you must add a connection to your storage bucket.
- In Migrate, navigate to Advanced > Migrate Services.
- In the Centralised Logging section, select Add Connection.
- Choose your storage platform and click Next.
- Enter the required information for your storage bucket. Ensure you have followed the prerequisite articles to gather the necessary details.
-
- If the test passes, click Save & Close.
- If the test fails, verify that you have entered the correct information and met all prerequisites.
The connection will now be tested.
Once the connection is successfully established, the status of centralised logging will update to "Connected", indicating that it is enabled and linked to the storage bucket.
Disabling Centralised Self-Hosted logging
To disable centralised logging, simply remove the connection by clicking the "Remove connection" button on the Migrate services page.
Allow CloudM support to view logs
After enabling centralised logging, you can grant support access to the storage bucket by toggling on the "Allow CloudM support to view logs" option.
Enabling this option applies the necessary permissions to the storage bucket, allowing the support team to access your logs from a centralised location.
Once enabled, a link will be displayed on the screen. Share this link with the support team when raising your ticket to help expedite troubleshooting.
If needed, you can revoke access at any time by disabling this option.
Migration Batch level configuration
Once centralised logging is enabled in the Migrate services area, it will automatically apply to any newly created migration batches. However, for existing migration batches, this must be enabled manually. Follow the steps below to enable centralised logging for an existing migration batch:
- Open the migration batch and navigate to Configuration (Step 2) > Advanced Settings > Logging.
- Enable the "Centralised logging" option.
- Set the trace level to "Trace".
- Click Next to save your configuration.
This ensures that centralised logging is active for your current migration batch, allowing trace level logs and configurations to be sent directly to your specified storage bucket.
Alternatively, if you do not want the logs for a specific migration batch to be sent to your storage bucket, you can disable the Centralised logging setting for that batch. In this case, the logs will be stored on the migration servers instead.
Changing the storage bucket
If you decide to change the storage bucket during a migration, follow the steps below:
- Navigate to Advanced > Migrate Services.
- Click "Edit Connection".
- Enter the information for your new storage bucket.
- Click Next to run the connection test.
Once the test has passed successfully and the status is shown as Connected, you must also restart the CloudM Migrate service on all migration servers.
This can be performed within the CloudM Migrate Service Manager.
Upload process
After the migration is complete, the logs will be uploaded to the specified Cloud Storage bucket and then removed from the migration server.
On the Migrate services page, the Pending operations column will display the status of any remaining tasks, including the upload of logs to Cloud Storage. When a green checkmark appears in this column (as shown below), it confirms that the logs have been successfully uploaded. At this point, you may proceed to shut down or delete the migration server if necessary.