Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Dokumen ini menjelaskan cara menyelesaikan masalah terkait pemantauan pemakaian
pemesanan
resource zona Compute Engine menggunakan Cloud Monitoring.
Gagal mengakses Cloud Monitoring
Masalah: Error ini terjadi saat Anda tidak dapat mengakses Monitoring.
Penyelesaian: Pastikan Anda memberikan akses ke Cloud Monitoring ke project saat ini, atau organisasi tempat project saat ini berada dapat memberikan akses untuk melakukannya.
Gagal melihat deret waktu pemesanan
Masalah: Error ini terjadi saat Anda tidak dapat mengakses dan melihat deret waktu
pemesanan.
Penyelesaian: Setelah pemesanan dibuat, deret waktunya akan tersedia
dalam waktu 30 menit. Jika Anda tidak dapat mengakses dan melihat deret waktu pemesanan setelah jangka waktu ini, coba salah satu opsi berikut:
Pastikan Anda berada dalam project yang sama tempat pemesanan dibuat.
Anda hanya dapat mengakses dan melihat deret waktu pemesanan yang dibuat dalam
project saat ini.
Menghapus pemesanan juga akan menghapus deret waktunya. Deret waktu tidak dapat dipulihkan.
Kueri MQL gagal melakukan operasi
Masalah: Error ini terjadi saat Anda mencoba menjalankan kueri MQL tanpa menentukan operasi | condition atau | absent_for.
Penyelesaian: Saat membuat kondisi pemberitahuan berbasis MQL, pastikan untuk menentukan salah satu operasi berikut di akhir kueri:
Untuk pemberitahuan nilai minimum, tentukan condition.
Untuk pemberitahuan ketidakhadiran, tentukan
absent_for.
[[["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-19 UTC."],[[["\u003cp\u003eThis document guides you through troubleshooting issues related to monitoring the consumption of Compute Engine zonal resource reservations using Cloud Monitoring.\u003c/p\u003e\n"],["\u003cp\u003eIf you encounter problems accessing Cloud Monitoring, ensure you have granted the necessary access permissions to the project or organization.\u003c/p\u003e\n"],["\u003cp\u003eIf you cannot view the time series of a reservation, verify that the reservation exists, that you are in the correct project, and note that time series are only available 30 minutes after creation, and cannot be recovered upon reservation deletion.\u003c/p\u003e\n"],["\u003cp\u003eWhen using MQL queries for alerts, you must include either a \u003ccode\u003e| condition\u003c/code\u003e operation for threshold alerts or a \u003ccode\u003e| absent_for\u003c/code\u003e operation for absence alerts at the end of the query.\u003c/p\u003e\n"]]],[],null,["# Troubleshooting reservation monitoring\n\n*** ** * ** ***\n\nThis document explains how to resolve issues with monitoring the consumption of [reservations](/compute/docs/instances/reservations-overview) of Compute Engine zonal resources by using Cloud Monitoring.\n\nFail to access Cloud Monitoring\n-------------------------------\n\n**Issue:** This error occurs when you can't access Monitoring.\n\n**Resolution:** Make sure that you\n[grant access to Cloud Monitoring](/monitoring/access-control#grant-monitoring-access)\nto the current project, or the organization where the current project is located\ngrants access to it.\n\nFail to view the time series of a reservation\n---------------------------------------------\n\n**Issue:** This error occurs when you can't access and view the time series of a\nreservation.\n\n**Resolution:** After creating a reservation, its time series becomes available\nwithin 30 minutes. If you can't access and view the time series of a reservation\nafter this timeframe, try one of the following:\n\n- To make sure that a reservation exists,\n [view the details of the reservation](/compute/docs/instances/reservations-view#describe-reservations).\n\n- If you can't view the details of a reservation:\n\n - Make sure that you're in the same project where the reservation was created.\n You can only access and view the time series of a reservation created in the\n current project.\n\n - Deleting a reservation also deletes its time series. The time series can't\n be recovered.\n\nMQL query misses an operation\n-----------------------------\n\n**Issue:** This error occurs when you attempt to run a MQL query without\nspecifying a `| condition` or `| absent_for` operation.\n\n**Resolution:** When creating an MQL-based alert condition, make sure to specify\none of the following operations at the end of your query:\n\n- For threshold alerts, specify\n [`condition`](/monitoring/mql/reference#condition-tabop).\n\n- For absence alerts, specify\n [`absent_for`](/monitoring/mql/reference#absent_for-tabop).\n\nFor more information, see [Alerting policies with MQL](/monitoring/mql/alerts)."]]
