Database Migration Service collects and displays migration job metrics that represent the health and progress of your data migration process.
The following table lists and describes the migration job metrics that you can view on the migration job details page. You can view the following metrics for all databases included in your migration job or only the databases that you selected for migration:
Migration metric
Description
Replication delay
Use this metric when you consider performing a promotion of a
continuous migration. Replication delay should be zero at the time of
the promotion in order to avoid data loss. Note this metric is only
relevant in the change data capture (CDC) phase. For more information on job promotion, see
Promote a
migration.
Storage usage in total bytes
Reflects how many GB are being used by the destination
AlloyDB for PostgreSQL instance. Use this metric to get a rough indication
of migration job progress.
You can use the following metrics to monitor your migrations:
The migration_job/initial_sync_complete metric indicates when the full dump phase is complete for a specific database or the entire migration job. You can view this metric on a migration level or a database level by applying the database label. If the database label is present, the metric value is for that particular database. If the label is not populated, the metric value is for the entire migration job.
The migration_job/max_replica_bytes_lag metric shows the size of log data that are not yet replicated to the destination. You can view this metric on a migration level or a database level by applying the database label. If the database label is present, the metric value is for that particular database. If the label is not populated, the metric value is for the entire migration job.
The migration_job/max_replica_sec_lag metric shows the time (in seconds) that the destination database is behind the source database. You can view this metric only at the migration level.
[[["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 provides metrics to monitor the health and progress of data migration jobs.\u003c/p\u003e\n"],["\u003cp\u003eReplication delay, which is crucial for avoiding data loss during continuous migration promotion, is a key metric, especially in the change data capture (CDC) phase.\u003c/p\u003e\n"],["\u003cp\u003eStorage usage in total bytes provides a general indication of the migration job's progress on the destination AlloyDB for PostgreSQL instance.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003emigration_job/initial_sync_complete\u003c/code\u003e metric signals when the full data dump phase is done, either for a specific database or the whole migration, offering granular insight into the data transfer process.\u003c/p\u003e\n"],["\u003cp\u003eMetrics such as \u003ccode\u003emigration_job/max_replica_bytes_lag\u003c/code\u003e and \u003ccode\u003emigration_job/max_replica_sec_lag\u003c/code\u003e provide insight into the lag between source and destination, helping to gauge the real-time synchronization status.\u003c/p\u003e\n"]]],[],null,["# Migration job metrics\n\n\u003cbr /\u003e\n\n[MySQL](/database-migration/docs/mysql/migration-job-metrics \"View this page for the MySQL version of Database Migration Service.\") \\| [PostgreSQL](/database-migration/docs/postgres/migration-job-metrics \"View this page for the PostgreSQL version of Database Migration Service.\") \\| PostgreSQL to AlloyDB\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nDatabase Migration Service collects and displays migration job metrics that represent the health and progress of your data migration process.\n\nThe following table lists and describes the migration job metrics that you can view on the migration job details page. You can view the following metrics for all databases included in your migration job or only the databases that you selected for migration:\n\nYou can view all [Database Migration Service Cloud Monitoring metrics that relate to migration job performance](/monitoring/api/metrics_gcp_d_h#gcp-datamigration) in the Metrics Explorer. To view each diagram directly in Cloud Monitoring, click more_vert**More chart options \\\u003e View in Metrics Explorer** .\n\n\u003cbr /\u003e\n\nYou can use the following metrics to monitor your migrations:\n\n- The [`migration_job/initial_sync_complete`](/monitoring/api/metrics_gcp_d_h#datamigration/migration_job/initial_sync_complete) metric indicates when the full dump phase is complete for a specific database or the entire migration job. You can view this metric on a migration level or a database level by applying the `database` label. If the database label is present, the metric value is for that particular database. If the label is not populated, the metric value is for the entire migration job.\n- The [`migration_job/max_replica_bytes_lag`](/monitoring/api/metrics_gcp_d_h#datamigration/migration_job/max_replica_bytes_lag) metric shows the size of log data that are not yet replicated to the destination. You can view this metric on a migration level or a database level by applying the `database` label. If the database label is present, the metric value is for that particular database. If the label is not populated, the metric value is for the entire migration job.\n- The [`migration_job/max_replica_sec_lag`](/monitoring/api/metrics_gcp_d_h#datamigration/migration_job/max_replica_sec_lag) metric shows the time (in seconds) that the destination database is behind the source database. You can view this metric only at the migration level.\n\nFor more information about the Metrics Explorer, see [Create charts with Metrics Explorer](/monitoring/charts/metrics-explorer)."]]
