Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Database Migration Service mengumpulkan dan menampilkan metrik tugas migrasi yang menunjukkan kondisi dan progres proses migrasi data Anda. Halaman ini menjelaskan area berikut yang terkait dengan metrik tugas migrasi:
Metrik yang tersedia di Cloud Monitoring menjelaskan semua metrik
yang terkait dengan performa tugas migrasi, termasuk metrik yang ditampilkan dari
cluster tujuan PostgreSQL.
Metrik yang tersedia di halaman detail tugas migrasi
Halaman detail tugas migrasi menampilkan beberapa diagram yang dapat membantu Anda memahami
status dan progres tugas migrasi saat ini. Anda dapat memfilter
informasi dalam diagram ini untuk setiap database yang disertakan dalam tugas migrasi.
Gambar 1. Diagram kemampuan pengamatan contoh di Database Migration Service.
(klik untuk memperbesar)
Luaskan bagian berikut untuk mempelajari lebih lanjut setiap diagram dan metrik terkaitnya. Database Migration Service memigrasikan satu database untuk migrasi Oracle heterogen. Setiap metrik menampilkan data yang relevan
dengan database yang Anda migrasikan.
Throughput
Diagram Throughput menggunakan metrik
migration_job/write_bytes_count untuk menunjukkan
jumlah data (dalam byte) yang telah ditulis Database Migration Service ke database tujuan Anda. Metrik ini diambil sampelnya setiap 60 detik. Anda dapat menggunakannya untuk mengamati kecepatan penulisan migrasi Anda.
Penggunaan penyimpanan dalam total byte
Diagram Penggunaan penyimpanan dalam total byte menggunakan metrik
cluster/storage/usage AlloyDB untuk PostgreSQL untuk menunjukkan jumlah data
(dalam byte) yang disimpan dalam database yang dimigrasikan di instance
AlloyDB untuk PostgreSQL tujuan Anda. Anda dapat menggunakan informasi ini untuk memperkirakan progres
tugas migrasi Anda.
Penundaan replikasi
Diagram Penundaan replikasi menggunakan metrik
migration_job/max_replica_sec_lag untuk merepresentasikan
perbedaan waktu antara saat Database Migration Service mulai
membaca informasi Pengambilan Data Perubahan (CDC) di sumber Anda, dan saat
informasi tersebut direplikasi sepenuhnya di tujuan Anda.
Anda dapat menggunakan informasi ini untuk memperkirakan kapan harus
mempromosikan tugas migrasi
(Anda ingin memulai proses penghentian saat jeda replikasi paling rendah).
Melihat metrik di halaman detail tugas migrasi
Untuk melihat diagram metrik di halaman detail tugas migrasi, lakukan langkah-langkah berikut:
Di konsol Google Cloud , buka halaman Tugas migrasi.
Jumlah byte yang ditulis ke tujuan. Dibuat sampelnya setiap 60 detik. Setelah sampelnya dibuat, data tidak akan terlihat selama maksimal 180 detik. database: Nama database.
migration_job/max_replica_bytes_lagBETA Byte jeda maksimum data tugas migrasi.
Keterlambatan replikasi saat ini, yang digabungkan di semua data tugas migrasi. Dibuat sampelnya setiap 60 detik. Setelah sampelnya dibuat, data tidak akan terlihat selama maksimal 180 detik. database: Nama database.
migration_job/max_replica_sec_lagBETA Keterlambatan maksimum dalam detik data tugas migrasi
Keterlambatan replikasi saat ini, yang digabungkan di semua data tugas migrasi. Dibuat sampelnya setiap 60 detik. Setelah sampelnya dibuat, data tidak akan terlihat selama maksimal 180 detik. database: Nama database.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-05 UTC."],[[["\u003cp\u003eDatabase Migration Service provides metrics to monitor the health and progress of data migration jobs.\u003c/p\u003e\n"],["\u003cp\u003eThe replication delay metric is crucial for continuous migrations, indicating the lag between source and destination databases.\u003c/p\u003e\n"],["\u003cp\u003eA replication delay of zero is necessary when promoting a continuous migration to prevent data loss.\u003c/p\u003e\n"],["\u003cp\u003eThe replication delay metric is only available in the incremental load phase.\u003c/p\u003e\n"]]],[],null,["Database Migration Service collects and displays migration job metrics that represent the\nhealth and progress of your data migration process. This page describes the\nfollowing areas associated with migration job metrics:\n\n- [Metrics available on the migration job details page](#job-details-page) covers the\n observability information you can view directly in Database Migration Service\n on the migration job details page.\n\n- [Metrics available in Cloud Monitoring](#monitoring-view) describes all metrics\n related to migration job performance, including the metrics surfaced from\n the PostgreSQL destination cluster.\n\nMetrics available on the migration job details page\n\nThe migration job details page shows several diagrams that can help you understand\nthe current state and progress of your migration job. Some diagrams provide\ndatabase-level information, while others focus on table-level data.\n[](#lightbox-trigger) **Figure 1.** Sample observability diagrams in Database Migration Service. (click to enlarge)\n\nExpand the following sections to learn more about each diagram and its associated\nmetric. \n\nThroughput\n\nThe **Throughput** diagram uses the\n[`migration_job/write_bytes_count`](/monitoring/api/metrics_gcp_d_h#datamigration/migration_job/write_bytes_count) metric to represent\nhow much data (in bytes) Database Migration Service has written to your destination\ndatabase. This metric is sampled every 60 seconds. You can use it to observe\nthe write speed of your migration.\n\nThis metric is available in the aggregated view, as well as separately\nfor each table included in your migration job.\n\nFull dump volume\n\nThe **Full dump volume** diagram shows the progress of the full dump phase\nexpressed as the percentage of total full dump data migrated.\nThis metric is available in the aggregated view, as well as separately\nfor each table included in your migration job.\n\n- The aggregated view diagram uses the `migration_job/fulldump_progress_percentage` metric.\n- The table-level diagrams use the `migration_job/fulldump_progress_percentage_per_object` metric.\n\nStorage usage in total bytes\n\nThe **Storage usage in total bytes** diagram uses the AlloyDB for PostgreSQL\n[`cluster/storage/usage`](/monitoring/api/metrics_gcp_a_b#alloydb/cluster/storage/usage) metric to show how much data\n(in bytes) is stored in the migrated database in your destination\nAlloyDB for PostgreSQL instance. You can use this information to estimate the progress\nof your migration job.\n\nReplication delay\n\nThe **Replication delay** diagram uses the\n[`migration_job/max_replica_sec_lag`](/monitoring/api/metrics_gcp_d_h#datamigration/migration_job/max_replica_sec_lag) metric to represent\nthe time difference between the moment when Database Migration Service starts\nreading Change Data Capture (CDC) information in your source, and the moment\nwhen that information is fully replicated in your destination.\nYou can use this information to estimate when to\n[promote the migration job](/database-migration/docs/oracle-to-alloydb/finalize-migration)\n(you want to begin the cutoff process when replication lag is the lowest).\n\nView metrics on the migration job details page\n\nTo view metric diagrams on the migration job details page, perform the following\nsteps:\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 your migration job.\n\n The migration job details page opens.\n3. In the **Monitoring** section, use the **View** menu to adjust\n which diagrams you want to display:\n\n - To view metrics aggregated for the whole migration job, click **View** \\\u003e **Aggregated**.\n - To view table-level metrics, click **View** \\\u003e **Tables**, and then select your tables.\n\nMetrics available in Cloud Monitoring\n\nThe following table describes all migration job metrics you can use to\n[create charts in Metrics Explorer](/monitoring/charts/metrics-explorer)\nfor heterogeneous Oracle migrations. The\n[complete metrics Database Migration Service metrics reference](/monitoring/api/metrics_gcp)\nlists several additional metrics, but they are not available for\nheterogeneous Oracle migrations.\n\nYou can also use the\n[AlloyDB for PostgreSQL `alloydb/cluster/storage/usage` metric](/monitoring/api/metrics_gcp_a_b#alloydb/cluster/storage/usage)\nand compare it with the total size of your source databases to estimate\nthe migration job progress.\n\n| Metric type ^Launch stage^ Display name ||\n| Kind, Type, Unit Monitored resources | *Description* Labels |\n|-------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| `migration_job/fulldump_progress_percentage` ^BETA^ ***(project)*** Fulldump progress percentage ||\n| `GAUGE`, `DOUBLE`, `%` **[datamigration.googleapis.com/MigrationJob](/monitoring/api/resources#tag_datamigration.googleapis.com/MigrationJob)** | *Progress percentage of the initial fulldump of the migration job.. Sampled every 60 seconds. After sampling, data is not visible for up to 180 seconds.* |\n| `migration_job/fulldump_progress_percentage_per_object` ^BETA^ ***(project)*** Fulldump progress percentage per object ||\n| `GAUGE`, `DOUBLE`, `%` **[datamigration.googleapis.com/MigrationJob](/monitoring/api/resources#tag_datamigration.googleapis.com/MigrationJob)** | *Progress percentage of the initial fulldump of a single table in a migration job. Sampled every 60 seconds. After sampling, data is not visible for up to 180 seconds.* |\n| `migration_``job/``write_``bytes_``count` ^BETA^ Write Bytes Count ||\n| `DELTA`, `INT64`, `By` **[datamigration.googleapis.com/MigrationJob](/monitoring/api/resources#tag_datamigration.googleapis.com/MigrationJob)** | *Number of bytes written to the destination. Sampled every 60 seconds. After sampling, data is not visible for up to 180 seconds.* `database`: Database name. |\n| `migration_``job/``max_``replica_``bytes_``lag` ^BETA^ Max lag bytes of the migration job data. ||\n| `GAUGE`, `INT64`, `By` **[datamigration.googleapis.com/MigrationJob](/monitoring/api/resources#tag_datamigration.googleapis.com/MigrationJob)** | *Current replication lag, aggregated across all of the migration job's data. Sampled every 60 seconds. After sampling, data is not visible for up to 180 seconds.* `database`: Database name. |\n| `migration_``job/``max_``replica_``sec_``lag` ^BETA^ Max lag in seconds of the migration job data ||\n| `GAUGE`, `INT64`, `s` **[datamigration.googleapis.com/MigrationJob](/monitoring/api/resources#tag_datamigration.googleapis.com/MigrationJob)** | *Current replication lag, aggregated across all of the migration job's data. Sampled every 60 seconds. After sampling, data is not visible for up to 180 seconds.* `database`: Database name. |\n| `migration_job/unsupported_events_count` ^BETA^ ***(project)*** Unsupported Events Count ||\n| `DELTA`, `INT64`, `By` **[datamigration.googleapis.com/MigrationJob](/monitoring/api/resources#tag_datamigration.googleapis.com/MigrationJob)** | *Number of unsupported events per migration and per table. Sampled every 60 seconds. After sampling, data is not visible for up to 180 seconds.* |"]]
