The transaction logs capture detail about all objects processed by the bridge. When you run a bridge, you can download the transaction logs using a standalone console. You can also download the logs using the command line.
About the transaction logs
Use the transaction logs to review details about each object processed during the bridge. Because the logs display each object within the migration scope, they might take some time to fully load. The number of failed transactions shown for a bridge on the Google Workspace Migrate platform is the sum of the errors in this log and the execution log.
Download the logs using the console
Before you begin: Make sure the Google Workspace Migrate application is running in the taskbar before you launch the console (you can turn off the app in the taskbar after you have launched the console).
- In the Google Workspace Migrate platform, click Bridges.
- Point to your bridge and click Logs
Console Transaction Log.
- Accept the default options or select your console settings:
- Output path—Specify the path where the transaction logs are exported, for example c:\gwm\logs. If you leave this field empty, the logs are exported to the default installation path of Google Workspace Migrate or the directory where the system executes the console application.
- Max rows per file—Specify the number of rows per file. The maximum number of rows is 500,000 for each comma separated values (CSV) file.
- Zip the result—(On by default) Turn off to download the files unzipped.
- Click Confirm.
The console downloads the logs to your computer. When the download is complete, you get a message that shows the output path for the logs.
Download the logs using the command line
- On the same server that you installed Google Workspace Migrate, as an administrator, open a command prompt.
- To access the logs, run the tool using at least one of the required arguments. For details on the arguments, go to the table in this section.
- Preface the argument name with two dashes and separate it from the argument value with an equals sign:
Path-to-log-tool/AppBridge.Tools.LogsConsole.exe --projectId=Your-project-Id --executionId=Your-execution-Id --maxRows=number-of-rows --outputPath="name-of-path" --zipResult=true-or-false
- To find the path to the log tool:
- On the same server that you installed Google Workspace Migrate, navigate to the folder where the platform is installed (for example, C:\Program Files\Google Workspace Migrate\Google Workspace Migrate Platform).
- If you run the command prompt from this folder, you don’t need to specify the path.
- If you run the command prompt outside the folder, you must add the Path-to-log-tool variable.
- Press confirm.
The system downloads the logs to your computer.
|
Argument name All arguments are case sensitive |
Description of argument value |
| projectId (Required) |
The hash ID of the project associated with the executed bridge.
To find the hash ID:
|
| executionId (Required) |
The hash ID of the most recent execution of the bridge.
To find the hash ID:
|
| maxRows | An integer that limits the number of rows in each downloaded CSV file. The default is 500,000 (if not specified). |
| outputPath |
A string that indicates the path of the target directory for the transaction logs' output. Enclose the path in quotation marks. If this value isn't set, the logs are exported to the default installation path of Google Workspace Migrate or the directory where the console application is executed. |
| zipResult | A boolean (true or false) that determines whether the downloaded CSV files are compressed into a zip file. The files are zipped by default. |
Examples
Example 1: Accept all of the default options
Path-to-log-tool/AppBridge.Tools.LogsConsole.exe --projectId=Your-project-Id --executionId=Your-execution-Id
Example 2: Specify all optional values
Path-to-log-tool/AppBridge.Tools.LogsConsole.exe --projectId=Your-project-Id --executionId=Your-execution-Id --maxRows=100000 --outputPath="C:\Users\YourUsername\Desktop\Output folder" --zipResult=false