Memantau dan mengelola penggunaan kuota Data Boost
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Spanner Data Boost tunduk pada kuota yang membatasi jumlah panggilan ExecuteStreamingSQL dan StreamingRead serentak yang dijalankan per project dan per region. Jika jumlah permintaan serentak melebihi kuota, permintaan akan gagal
dengan error RESOURCE EXHAUSTED.
Memeriksa kuota
Untuk memeriksa kuota serentak di project Anda, ikuti langkah-langkah berikut:
Tambahkan filter untuk quota_metric sama dengan
spanner.googleapis.com/data_boost_quota.
Menetapkan pemberitahuan untuk penggunaan Data Boost
Anda dapat membuat kebijakan pemberitahuan yang memberi tahu Anda saat jumlah kueri partisi serentak yang meminta Data Boost (panggilan ExecuteStreamingSQL dan StreamingRead serentak) per project dan per region melebihi nilai minimum tertentu. Untuk melakukannya,
ikuti langkah-langkah berikut:
Di menu dropdown Select a metric, di kolom Filter by resource or
metric name, masukkan data_boost dan tekan Enter untuk mempersempit penelusuran.
Dalam daftar Select a metric, pilih
Cloud Spanner Instance > Instance > Processing Unit Second, lalu
klik Apply.
Lanjutkan dengan membuat kebijakan pemberitahuan dan tetapkan nilai minimum ke beberapa persentase kuota.
Misalnya, jika kuota defaultnya adalah 200 dan Anda ingin diberi tahu saat jumlah permintaan serentak mencapai 80% dari maksimum, masukkan 160 di kolom Nilai minimum.
Menangani error kuota
Jika rasio error kuota terlampaui tinggi, saat menggunakan Dataflow dengan
Data Boost, sebaiknya sesuaikan jumlah maksimum pekerja
dalam tugas Dataflow untuk menghindari melampaui kuota Data Boost. Anda juga dapat mengajukan permohonan kuota yang lebih tinggi.
Memblokir akun utama agar tidak menggunakan resource Data Boost
Jika satu akun utama secara konsisten melebihi jumlah resource Data Boost yang dapat digunakannya secara wajar, Anda dapat memblokir akun utama tersebut agar tidak menggunakan resource Data Boost dengan mencabut izin Identity and Access Management (IAM) spanner.databases.useDataBoost dari akun utama tersebut. Anda dapat mengotomatiskan pencabutan izin dengan mengonfigurasi saluran notifikasi pemberitahuan sebagai webhook yang memanggil Cloud Function. Untuk informasi selengkapnya, lihat topik berikut:
[[["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-08-11 UTC."],[],[],null,["# Monitor and manage Data Boost quota usage\n\n\u003cbr /\u003e\n\nSpanner Data Boost is subject to quotas that limit the number of concurrent\n`ExecuteStreamingSQL` and `StreamingRead` calls executing per project and per\nregion. When the number of concurrent requests exceeds the quota, requests fail\nwith `RESOURCE EXHAUSTED` errors.\n\nCheck your quota\n----------------\n\nTo check the concurrency quota in your project, follow these steps:\n\n1. Go to the Quotas page in the Google Cloud console.\n\n [Go to Quotas](https://console.cloud.google.com/iam-admin/quotas)\n2. In the **Filter** field, enter `databoost`. Then, in the list, select\n **DataBoostQuotaPerProjectPerRegion**.\n\n3. In the resulting table, locate your region and view the limit for that\n region.\n\n| **Note:** To check the default quota for regions, select **DataBoost Operations per\n| region (default)** instead.\n\nMonitor quota usage\n-------------------\n\nTo monitor your quota usage, follow these steps:\n\n1. In the Google Cloud console, go to **Monitoring** . \n [Go to Monitoring](https://console.cloud.google.com/monitoring)\n2. If **Metrics Explorer** is shown in the navigation menu, select it. Otherwise, click **Resources** , and then select **Metrics Explorer**.\n3. At the top of the page, select a time interval.\n4. In the **Metric** dropdown list, in the **Filter by resource or metric\n name** field, enter `consumer` and press `Enter` to narrow the search.\n5. In the list, select **Consumer Quota \\\u003e Quota \\\u003e Concurrent Quota usage** , and then click **Apply**.\n6. Click **+ ADD FILTER** to create a filter.\n7. In the **Label 1** dropdown list, select **quota_metric**.\n8. In the **Value 1** text field, enter or select\n **spanner.googleapis.com/data_boost_quota**.\n\n Metrics explorer shows a line chart of quota usage by region.\n9. Optional: Under **Display** , for **Widget type** , select **Stacked bar chart**.\n\nMonitor quota errors\n--------------------\n\nTo monitor quota errors, follow these steps:\n\n1. In Metrics explorer, select the metric\n **Consumer Quota \\\u003e Quota \\\u003e Quota exceeded error**.\n\n2. Add a filter for **quota_metric** equals\n **spanner.googleapis.com/data_boost_quota**.\n\nSet an alert for Data Boost usage\n---------------------------------\n\nYou can create an alert policy that notifies you when the number of concurrent\n[partitioned queries](/spanner/docs/reads#read_data_in_parallel) that request\nData Boost (concurrent `ExecuteStreamingSQL` and `StreamingRead`\ncalls) per project and per region exceeds a particular threshold. To do so,\nfollow these steps:\n\n1. Follow the instructions in [Create metric-threshold alerting policies](https://cloud.google.com/monitoring/alerts/using-alerting-ui).\n2. In the **Select a metric** dropdown list, in the **Filter by resource or\n metric name** field, enter `data_boost` and press `Enter` to narrow the search.\n3. In the **Select a metric** list, select **Cloud Spanner Instance \\\u003e Instance \\\u003e Processing Unit Second** , and then click **Apply**.\n4. Continue with creating an alert policy and set the threshold to some\n percentage of the quota.\n\n For example if the default quota is 200 and you want to be notified when the\n number of concurrent requests reaches 80% of maximum, enter 160 in the\n **Threshold value** field.\n\nHandle quota errors\n-------------------\n\nIf the rate of quota-exceeded errors is high, when using Dataflow with\nData Boost, we recommend that you adjust the maximum number of\nworkers in your Dataflow job to avoid exceeding the\nData Boost quota. You can also apply for a higher quota.\n\nBlock a principal from consuming Data Boost resources\n-----------------------------------------------------\n\nIf one principal is consistently exceeding the amount of\nData Boost resources that they can be reasonably expected to\nconsume, you can block the principal from using Data Boost\nresources by revoking the `spanner.databases.useDataBoost` Identity and Access Management\n(IAM) permission from the principal. You can automate revoking\nthe permission by configuring an alert's notification channel as a webhook that\ninvokes a Cloud Function. For more information, see the following topics:\n\n- [Create a notification channel](https://cloud.google.com/monitoring/support/notification-options#creating_channels)\n- [Cloud Functions](https://cloud.google.com/functions)\n- [Remove database-level permissions](https://cloud.google.com/spanner/docs/grant-permissions#remove-iam-db-role)\n- [Modify the allow policy](https://cloud.google.com/iam/docs/granting-changing-revoking-access#modifying-policy)\n for sample code that revokes a role.\n\n | **Note:** A best practice is to add the `spanner.databases.useDataBoost` permission to a custom IAM role.\n\nWhat's next\n-----------\n\n- Learn about Data Boost in [Data Boost overview](/spanner/docs/databoost/databoost-overview)."]]
