Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Halaman ini membahas metrik yang digunakan untuk memantau rasio penggunaan data dari bucket Cloud Storage Anda, serta cara meminta bandwidth keluar tambahan untuk kuota yang berbeda jika Anda membutuhkan lebih dari kuota default.
Untuk mengetahui petunjuk tentang cara mengakses data pemantauan di Cloud Storage, lihat Mengakses data pemantauan.
Pengantar
Cloud Storage menyediakan pemantauan bandwidth untuk melacak penggunaan
bandwidth dari bucket project Anda ke layanan Google Cloud lainnya. Pemantauan
bandwidth digabungkan berdasarkan wilayah dan melacak penggunaan selama 6 minggu terakhir.
Sebelum memantau penggunaan bandwidth, tinjau persyaratan berikut:
Bandwidth traffic keluar mengacu pada kecepatan pengambilan data dari bucket Anda selama menyelesaikan permintaan yang dibuat ke Cloud Storage.
Bandwidth traffic keluar Google mengacu pada data yang diambil dari bucket Anda yang ditujukan untuk layanan Google lainnya, seperti Compute Engine.
Bandwidth traffic keluar internet mengacu pada data yang diambil dari bucket Anda yang ditayangkan ke Internet, seperti data yang didownload langsung ke komputer lokal Anda atau data yang diambil oleh Cloud CDN untuk ditayangkan ke Internet.
Akses keluar jaringan mengacu pada kecepatan pengiriman data melalui jaringan
dari bucket Anda ke pemohon.
Dalam operasi normal, bandwidth keluar dan traffic keluar jaringan biasanya hampir sama; namun, dalam beberapa kasus, bandwidth keluar dapat jauh lebih besar daripada traffic keluar jaringan. Koneksi rusak, permintaan yang dibatalkan, dan permintaan parsial adalah kasus-kasus di mana data yang diambil mungkin lebih besar daripada data yang pada akhirnya dikirim.
Metrik pemantauan bandwidth
Data penggunaan bandwidth berikut tersedia untuk pemantauan:
Bandwidth keluar Google per detik per region: memantau penggunaan bandwidth keluar Google untuk bucket di project Anda yang berada di region.
Bandwidth keluar Google region ganda per detik per region per lokasi region ganda: memantau penggunaan bandwidth keluar Google untuk bucket di project Anda yang berada di region ganda.
Bandwidth traffic keluar Google multi-region per detik per region: memantau penggunaan bandwidth traffic keluar Google untuk bucket di project Anda yang berada di multi-region.
Bandwidth keluar internet per detik per region: memantau penggunaan bandwidth keluar internet untuk bucket di project Anda yang berada di region.
Bandwidth keluar internet region ganda per detik per region per lokasi region ganda: memantau penggunaan bandwidth keluar internet untuk bucket di project Anda yang berada di region ganda.
Bandwidth keluar internet multi-region per detik per region: memantau penggunaan bandwidth keluar internet untuk bucket di project Anda yang berada di multi-region.
Pemberitahuan Monitoring
Anda dapat menggunakan kebijakan pemberitahuan Monitoring untuk memberi tahu Anda saat
metrik seperti storage.googleapis.com/google_egress_bandwidth,
storage.googleapis.com/dualregion_google_egress_bandwidth, dan
storage.googleapis.com/multiregion_google_egress_bandwidth mendekati batas
kuota.
Selain pemantauan bandwidth Cloud Storage, Anda dapat menggunakan
metrik network/sent_bytes_count untuk mengukur keluar jaringan Cloud Storage. Hal ini berguna untuk memperkirakan penggunaan bandwidth untuk bucket tertentu, karena pemantauan bandwidth melacak penggunaan bandwidth menurut lokasi dan project.
Saat menggunakan metrik jaringan ini, perhatikan hal-hal berikut:
network/sent_bytes_count mengukur dalam byte, sedangkan metrik
jaringan standar biasanya menggunakan bit. Misalnya, pengukuran 1 GiBps untuk
network/sent_bytes_count setara dengan 8 Gibps.
network/sent_bytes_count melacak semua traffic yang dikirim melalui jaringan, bukan
hanya traffic keluar ke layanan Google Cloud yang ditempatkan bersama. Dengan demikian,
network/sent_bytes_count biasanya lebih besar dari penggunaan bandwidth.
Dalam beberapa kasus, network/sent_bytes_count mungkin lebih sedikit dari penggunaan
bandwidth karena peristiwa seperti koneksi yang rusak, permintaan yang dibatalkan, dan
permintaan parsial.
Metrik network/sent_bytes_count diambil sampelnya setiap 60 detik. Jika
traffic naik-turun, permintaan mungkin di-throttle sesaat
meskipun traffic keluar rata-rata selama 60 detik berada di bawah batas.
[[["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."],[],[],null,["This page discusses metrics used to monitor data usage rates from your\nCloud Storage buckets, as well as how to request additional egress\nbandwidth for different quotas if you need more than the [default quota](/storage/quotas#bandwidth).\n\nFor instructions on accessing monitoring data in Cloud Storage, see\n[Access monitoring data](/storage/docs/access-monitoring).\n\nIntroduction\n\nCloud Storage provides bandwidth monitoring for you to track bandwidth\nusage from your project's buckets to other Google Cloud services. Bandwidth\nmonitoring is aggregated by region and tracks usage for the last 6 weeks.\n\nBefore monitoring bandwidth usage, review the following terms:\n\n- *Egress bandwidth* refers to the rate at which data is retrieved from your\n buckets in the course of completing requests made to Cloud Storage.\n\n - *Google egress bandwidth* refers to data retrieved from your buckets that\n is destined for other Google services, such as Compute Engine.\n\n - *Internet egress bandwidth* refers to data retrieved from your buckets\n that is served to the Internet, such as data downloaded directly to\n your local computer or data retrieved by Cloud CDN for serving to the\n Internet.\n\n- *Network egress* refers to the rate at which data is sent over the network\n from your buckets to requesters.\n\nIn normal operation, egress bandwidth and network egress are typically about the\nsame; however, in some cases egress bandwidth can be meaningfully greater than\nnetwork egress. Broken connections, cancelled requests, and partial requests are\ncases where the data retrieved can be greater than the data that's ultimately\nsent.\n\nBandwidth monitoring metrics\n\nThe following bandwidth usage data is available for monitoring:\n\n- Google egress bandwidth per second per region: monitors Google egress\n bandwidth usage for buckets in your project that are located in regions.\n\n- Dual-region Google egress bandwidth per second per region per\n dual-region location: monitors Google egress bandwidth usage for buckets in\n your project that are located in dual-regions.\n\n- Multi-region Google egress bandwidth per second per region: monitors\n Google egress bandwidth usage for buckets in your project that\n are located in multi-regions.\n\n- Internet egress bandwidth per second per region: monitors Internet\n egress bandwidth usage for buckets in your project that\n are located in regions.\n\n- Dual-region internet egress bandwidth per second per region per dual-region\n location: monitors Internet egress bandwidth usage for buckets in your project\n that are located in dual-regions.\n\n- Multi-region internet egress bandwidth per second per region: monitors\n Internet egress bandwidth usage for buckets in your project that\n are located in multi-regions.\n\nMonitoring alerts\n\nYou can use Monitoring alerting policies to inform you when\nmetrics such as `storage.googleapis.com/google_egress_bandwidth`,\n`storage.googleapis.com/dualregion_google_egress_bandwidth`, and\n`storage.googleapis.com/multiregion_google_egress_bandwidth` approach a quota\nlimit.\n\n- For an overview of Monitoring alerts, see\n [Introduction to alerting](/monitoring/alerts).\n\n- To get started with Monitoring alerts using the\n Google Cloud console, see [Create metric-based alert policies](/monitoring/alerts/using-alerting-ui).\n\n- For examples of Monitoring alerts, see\n [Chart and monitor quota metrics](/monitoring/alerts/using-quota-metrics).\n\nNetwork monitoring\n\nIn addition to Cloud Storage bandwidth monitoring, you can use the\n[`network/sent_bytes_count`](/monitoring/api/metrics_gcp_p_z#gcp-storage) metric to measure Cloud Storage\nnetwork egress. This is useful for approximating bandwidth usage for specific\nbuckets, because bandwidth monitoring tracks bandwidth usage by location and\nproject.\n\nWhen using this networking metric, keep in mind the following:\n\n- `network/sent_bytes_count` uses bytes in its measurements, whereas typical\n networking metrics often use bits. For example, a 1 GiBps measurement for\n `network/sent_bytes_count` is equivalent to 8 Gibps.\n\n- `network/sent_bytes_count` tracks all the traffic sent over the network, not\n only egress to co-located Google Cloud services. As such,\n `network/sent_bytes_count` is typically greater than bandwidth usage.\n\n - In some cases, `network/sent_bytes_count` can be less than bandwidth usage due to events such as broken connections, cancelled requests, and partial requests.\n- `network/sent_bytes_count` metrics are sampled every 60 seconds. If the\n traffic is spiky, it's possible that requests are throttled for a short period\n of time even though the average egress over 60 seconds is below the limit.\n\nRequest more bandwidth\n\nThe following instructions apply when requesting egress bandwidth of up to 1\nTbps for Cloud Storage buckets:\n\n1. Make sure you have enabled the\n [Cloud Storage service `storage.googleapis.com`](https://console.cloud.google.com/apis/library/storage.googleapis.com).\n\n2. In the Google Cloud console, go to the IAM **Quotas \\& System Limits** page.\n\n [Go\n to Browser](https://console.cloud.google.com/iam-admin/quotas)\n3. In the **Filter** search bar, select the **Metric** property, then search\n for the metric for which you are requesting an increase:\n\n - Use `storage.googleapis.com/google_egress_bandwidth` to increase Google\n egress for your buckets located in regions.\n\n - Use `storage.googleapis.com/dualregion_google_egress_bandwidth` to increase\n Google egress for your buckets located in dual-regions.\n\n - Use `storage.googleapis.com/multiregion_google_egress_bandwidth` to\n increase Google egress for your buckets located in multi-regions.\n\n - Use `storage.googleapis.com/internet_egress_bandwidth` to increase Internet\n egress for your buckets located in regions.\n\n - Use `storage.googleapis.com/dualregion_internet_egress_bandwidth` to\n increase Internet egress for your buckets located in dual-regions.\n\n - Use `storage.googleapis.com/multiregion_internet_egress_bandwidth` to\n increase Internet egress for your buckets located in multi-regions.\n\n4. In the list of results, toggle the checkbox for the locations where you want\n to increase egress bandwidth. For the\n `storage.googleapis.com/dualregion_google_egress_bandwidth` and\n `storage.googleapis.com/dualregion_internet_egress_bandwidth` metrics, there\n must be non-zero historical usage of the metric before you can request an\n increase.\n\n5. Click **Edit Quotas**.\n\n6. Enter your requested quota and business justification.\n\n7. Click **Submit Request**.\n\nFor bandwidth requirements greater than 1 Tbps for egress from buckets in\nregions and dual-regions, contact your [Technical Account Manager](/tam) or Google\nrepresentative. Increase requests greater than 1 Tbps for egress from buckets\nin multi-regions are not supported.\n| **Important:** Granting and continuation of bandwidth quota increases is dependent on your project's history. For example, a project might have an existing bandwidth quota increase reduced or rescinded if the project is not in good standing.\n\nFor more information, see [View and manage quotas](/docs/quotas/view-manage).\n\nWhat's next\n\n- [Access bandwidth monitoring data](/storage/docs/access-monitoring).\n- [Monitor who accesses your Cloud Storage resources](/storage/docs/audit-logging).\n- [Create notifications](/storage/docs/reporting-changes) when an object is created, updated, or deleted."]]
