Stay organized with collections
Save and categorize content based on your preferences.
Database Migration Service uses Cloud Logging. You can access two log categories to
acquire detailed information on events that occur with relation to your migration
jobs: Database Migration Service logs, and the destination AlloyDB for PostgreSQL logs.
Each log entry contains a jsonPayload.textMessage field with a description to
help you better understand the event. There are different types of messages,
for example:
Sample log messages for the
datamigration.googleapis.com/MigrationJob resource
Log text message
Description
FULL DUMP read is completed for table: {SCHEMA_TABLE_NAME}
This message means that Database Migration Service finished reading
specific table data in your source database for the full dump phase.
This message indicates that the full dump phase for the table is
in an advanced stage and is likely to complete shortly.
Successfully loaded {NUMBER} FULL DUMP rows into table: {SCHEMA_TABLE_NAME}
This message means that Database Migration Service finished writing a batch of
rows into a specific table in your destination cluster during the full dump
phase.
Successfully applied {NUMBER} CDC rows into table: {SCHEMA_TABLE_NAME}
This message means that Database Migration Service finished writing a batch of
rows into a specific table in your destination cluster during the CDC phase.
Accessing data of table: {SCHEMA_TABLE_NAME} for data processing purpose
When you
use a CMEK
for your migration job, this message indicates that
Database Migration Service accessed the encryption key to process data
for a specific table.
AlloyDB for PostgreSQL cluster logs
AlloyDB for PostgreSQL also provides log entries for your destination cluster.
See the
AlloyDB for PostgreSQL logs reference in the Cloud Logging documentation.
View and query logs
To view your logs, perform the following:
In the Google Cloud console, go to the
Migration jobs page.
In the Jobs tab, click the display name of the migration job
for which you want to view logs.
The migration job details page opens.
On the migration job details page, click View logs and perform one
of the following:
To view migration job logs, select Migration job logs.
To view logs for your AlloyDB for PostgreSQL destination cluster,
select Destination instance logs.
The Logs Explorer page opens.
On the Logs Explorer page, you can use the drop-down menus
to modify the query and filter log entries. For example, to filter migration
job logs for events where Database Migration Service accessed a specific table in your
source database, you can use a query similar to the following:
resource.type="datamigration.googleapis.com/MigrationJob"
resource.labels.migration_job_id="MIGRATION_JOB_ID"
jsonPayload.textMessage:"Accessing data of table"
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-03 UTC."],[[["\u003cp\u003eDatabase Migration Service offers structured logs for \u003ccode\u003eMigrationJob\u003c/code\u003e, \u003ccode\u003eConnectionProfile\u003c/code\u003e, and \u003ccode\u003ePrivateConnection\u003c/code\u003e resources, detailing events like job creation or data reads.\u003c/p\u003e\n"],["\u003cp\u003eLogs contain a \u003ccode\u003ejsonPayload.textMessage\u003c/code\u003e field that provides descriptions of events, such as the completion of a table data read or the successful loading of rows into the destination.\u003c/p\u003e\n"],["\u003cp\u003eAlloyDB for PostgreSQL provides log entries for the destination cluster, which can be viewed through the Cloud Logging documentation.\u003c/p\u003e\n"],["\u003cp\u003eLogs can be accessed through the Google Cloud console's Migration jobs page, with options to view both migration job logs and destination instance logs.\u003c/p\u003e\n"],["\u003cp\u003eYou can filter logs in the Logs Explorer using queries, such as to identify when the service accesses data of a specific table.\u003c/p\u003e\n"]]],[],null,["# Logging\n\nDatabase Migration Service uses Cloud Logging. You can access two log categories to\nacquire detailed information on events that occur with relation to your migration\njobs: Database Migration Service logs, and the destination AlloyDB for PostgreSQL logs.\n\nDatabase Migration Service logs\n-------------------------------\n\nDatabase Migration Service for SQL Server to AlloyDB for PostgreSQL provides\n[structured logs](/logging/docs/structured-logging#structured_logging_special_fields) for the\n[`datamigration.googleapis.com/MigrationJob`](/database-migration/docs/reference/rest/v1/projects.locations.migrationJobs#resource:-migrationjob),\n[`datamigration.googleapis.com/ConnectionProfile`](/database-migration/docs/reference/rest/v1/projects.locations.connectionProfiles),\nand\n[`datamigration.googleapis.com/PrivateConnection`](/database-migration/docs/reference/rest/v1/projects.locations.privateConnections)\nresources.\nThese logs represent real-world events, such as when a migration job is created,\nwhen Database Migration Service reads information from your source database,\nor when a connection profile is edited.\n\nEach log entry contains a `jsonPayload.textMessage` field with a description to\nhelp you better understand the event. There are different types of messages,\nfor example:\n\nAlloyDB for PostgreSQL cluster logs\n-----------------------------------\n\nAlloyDB for PostgreSQL also provides log entries for your destination cluster.\nSee the\n[AlloyDB for PostgreSQL logs reference](/logging/docs/api/platform-logs#alloydb) in the Cloud Logging documentation.\n\nView and query logs\n-------------------\n\nTo view your logs, perform the following:\n\n1. In the Google Cloud console, go to the **Migration jobs** page.\n\n [Go to Migration jobs](https://console.cloud.google.com/dbmigration/migrations)\n2. In the **Jobs** tab, click the display name of the migration job for which you want to view logs.\n\n The migration job details page opens.\n3. On the migration job details page, click **View logs** and perform one of the following:\n - To view migration job logs, select **Migration job logs**.\n - To view logs for your AlloyDB for PostgreSQL destination cluster, select **Destination instance logs**.\n\n The **Logs Explorer** page opens.\n4. On the **Logs Explorer** page, you can use the drop-down menus to modify the query and filter log entries. For example, to filter migration job logs for events where Database Migration Service accessed a specific table in your source database, you can use a query similar to the following: \n\n ```bash\n resource.type=\"datamigration.googleapis.com/MigrationJob\"\n resource.labels.migration_job_id=\"\u003cvar translate=\"no\"\u003eMIGRATION_JOB_ID\u003c/var\u003e\"\n jsonPayload.textMessage:\"Accessing data of table\"\n ```\n\nWhat's next\n-----------\n\n- For more information on using Logs Explorer, see\n [View logs by using Logs Explorer](/logging/docs/view/logs-explorer-interface).\n\n- For a detailed reference of what fields are supported in Database Migration Service\n log entries, see\n [Database Migration Service logs reference](/logging/docs/api/platform-logs#cloud_database_migration_service).\n\n- To get a complete, step-by-step migration walkthrough, see\n [SQL Server to AlloyDB for PostgreSQL migration guide](/database-migration/docs/sqlserver-to-alloydb/guide)."]]
