Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Halaman ini membahas cara membuat dan menonaktifkan pemberitahuan Penagihan dan aturan pemberitahuan.
Sebelum memulai
Sebelum melanjutkan, pastikan Anda memiliki peran yang diperlukan berikut:
Pembuat PA MonitoringRule: membuat dan mengelola MonitoringRule resource
kustom. Minta Admin IAM Organisasi Anda untuk memberi Anda peran monitoringrule-pa-creator.
Membuat aturan pemberitahuan
Anda dapat membuat aturan pemberitahuan berdasarkan metrik invoice dan batas pembelanjaan menggunakan resource MonitoringRule di Observability API.
Lihat Membuat aturan pemberitahuan
untuk mengetahui petunjuk tentang cara membuat pemberitahuan menggunakan konsol GDC.
Untuk membuat aturan pemberitahuan, ikuti langkah-langkah berikut:
Buat file YAML, lalu tambahkan resource MonitoringRule dan
konten berikut:
Ganti TASK_ORDER dengan perintah tugas dan CLIN dengan nomor item baris kontrak Anda.
SEVERITY
Tingkat keseriusan aturan pemberitahuan. Nilai tingkat keseriusan mencakup error, critical, warning, dan info.
BILLING_CODE
Kode penagihan yang Anda tentukan untuk aturan pemberitahuan.
Contoh: "BILLING-100".
MESSAGE
Deskripsi pemberitahuan yang muncul saat aturan pemberitahuan berjalan.
Contoh: "Spending exceeded limit".
Terapkan isi file YAML dan tetapkan aturan pemberitahuan:
kubectlapply-fFILENAME.yaml
Membuat pemberitahuan nilai minimum pembelanjaan
Operator Infrastruktur (IO) Anda membuat kebijakan pemberitahuan batas pengeluaran di konsol GDC. Pemberitahuan nilai minimum pembelanjaan adalah pemberitahuan penagihan kustom yang menunjukkan
saat biaya penagihan melebihi nilai minimum yang Anda tetapkan. Misalnya, IO Anda membuat pemberitahuan biaya total penagihan dan mengonfigurasi pemberitahuan berdasarkan jumlah dolar tetap, atau sebagai persentase dari jumlah anggaran awal.
Untuk membuat pemberitahuan batas pembelanjaan dan pemberitahuan penagihan tingkat organisasi lainnya,
kirimkan permintaan ke IO Anda. Sertakan parameter berikut dalam permintaan Anda:
Nomor pesanan tugas (TO).
CLIN
Jumlah total anggaran untuk TO dan CLIN yang ditentukan.
Nilai minimum anggaran.
Menonaktifkan suara notifikasi
Anda dapat membisukan dan membatalkan pembisuan aturan pemberitahuan melalui konsol GDC.
Ikuti petunjuk di Membisukan notifikasi.
[[["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-04 UTC."],[[["\u003cp\u003eThis page guides you through the process of creating billing alert rules using the \u003ccode\u003eMonitoringRule\u003c/code\u003e resource in the Observability API, based on invoice metrics and spend thresholds.\u003c/p\u003e\n"],["\u003cp\u003eTo create an alert rule, you need to have the \u003ccode\u003emonitoringrule-pa-creator\u003c/code\u003e role and then set up a YAML file with specific parameters, such as the alert name, expression, severity, and message.\u003c/p\u003e\n"],["\u003cp\u003eSpend threshold alerts, which are custom billing alerts that notify when billing costs exceed a set amount, are created by your Infrastructure Operator (IO) through a request process that includes task order number, CLIN, total budget, and budget threshold.\u003c/p\u003e\n"],["\u003cp\u003eYou can silence and unsilence alert rules via the GDC console by following the provided instructions.\u003c/p\u003e\n"],["\u003cp\u003eThis page also contains instructions on how to set up billing notification channels.\u003c/p\u003e\n"]]],[],null,["# Manage billing alerts\n\nThis page covers creating and silencing Billing alerts and alert rules.\n\nBefore you begin\n----------------\n\nBefore continuing, ensure you have the following required role:\n\n- **MonitoringRule PA Creator** : create and manage `MonitoringRule` custom resources. Ask your Organization IAM Admin to grant you the `monitoringrule-pa-creator` role.\n\nCreate alert rules\n------------------\n\nYou can create alert rules based on invoice metrics and your spend thresholds\nusing the [`MonitoringRule`](/distributed-cloud/hosted/docs/latest/gdch/apis/service/monitoring/v1/monitoring-v1#monitoringrule)\nresource in the [Observability API](/distributed-cloud/hosted/docs/latest/gdch/apis/observability-api-overview).\n\nSee [Create alert rules](/distributed-cloud/hosted/docs/latest/gdch/platform/pa-user/create-alert-rules#create-rules)\nfor instructions on creating alerts using the GDC console.\n\nTo create an alert rule, work through the following steps:\n\n1. Create a YAML file, and add in the `MonitoringRule` resource and the\n following contents:\n\n apiVersion: monitoring.gdc.goog/v1\n kind: MonitoringRule\n metadata:\n name: \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-l devsite-syntax-l-Scalar devsite-syntax-l-Scalar-Plain\"\u003eMONITORING_RULE_NAME\u003c/span\u003e\u003c/var\u003e\n namespace: \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-l devsite-syntax-l-Scalar devsite-syntax-l-Scalar-Plain\"\u003ePROJECT\u003c/span\u003e\u003c/var\u003e\n spec:\n interval: \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-l devsite-syntax-l-Scalar devsite-syntax-l-Scalar-Plain\"\u003eINTERVAL\u003c/span\u003e\u003c/var\u003e\n limit: \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-l devsite-syntax-l-Scalar devsite-syntax-l-Scalar-Plain\"\u003eLIMIT\u003c/span\u003e\u003c/var\u003e\n alertRules:\n - alert: \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-l devsite-syntax-l-Scalar devsite-syntax-l-Scalar-Plain\"\u003eALERT\u003c/span\u003e\u003c/var\u003e\n expr: \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-l devsite-syntax-l-Scalar devsite-syntax-l-Scalar-Plain\"\u003eEXPRESSION\u003c/span\u003e\u003c/var\u003e\n labels:\n severity: \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-l devsite-syntax-l-Scalar devsite-syntax-l-Scalar-Plain\"\u003eSEVERITY\u003c/span\u003e\u003c/var\u003e\n code: \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-l devsite-syntax-l-Scalar devsite-syntax-l-Scalar-Plain\"\u003eBILLING_CODE\u003c/span\u003e\u003c/var\u003e\n resource: BILLING\n annotations:\n message: \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-l devsite-syntax-l-Scalar devsite-syntax-l-Scalar-Plain\"\u003eMESSAGE\u003c/span\u003e\u003c/var\u003e\n\n Replace the following variables:\n\n2. Apply the contents of the YAML file and set the alert rule:\n\n kubectl apply -f \u003cvar translate=\"no\"\u003eFILENAME\u003c/var\u003e.yaml\n\nCreate spend threshold alerts\n-----------------------------\n\nYour Infrastructure Operator (IO) creates spend threshold alert policies in\nthe GDC console. Spend threshold alerts are custom billing alerts that indicate\nwhen the billing costs exceed the threshold you set. For example, your IO creates billing\ntotal cost alerts and configures the alerts based on a fixed dollar amount, or as\na percentage of the initial budgeted amount.\n\nTo create spend threshold alerts and other organization-level billing alerts,\nsubmit a request to your IO. Include the following parameters in your request:\n\n- Task order (TO) number.\n- CLIN\n- The total budget amount for the specified TO and CLIN.\n- The budget threshold.\n\nSilence alerts\n--------------\n\nYou can silence and unsilence alert rules through the GDC console.\nFollow the instructions in [Silence an alert](/distributed-cloud/hosted/docs/latest/gdch/platform/pa-user/manage-alerts-and-policies#silence-an-alert).\n\nConfigure billing notifications\n-------------------------------\n\nTo configure billing notifications, follow the instructions in\n[Configure notification channels](/distributed-cloud/hosted/docs/latest/gdch/platform/pa-user/configure-notification-channels)."]]
