Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Ringkasan metrik sisi klien
Bigtable menyediakan metrik sisi klien yang dapat Anda gunakan bersama
dengan metrik sisi server untuk mengoptimalkan performa dan memecahkan masalah performa
jika terjadi.
Halaman ini memberikan ringkasan metrik sisi klien Bigtable dan
membahas kapan harus menggunakannya. Untuk petunjuk penyiapan dan konfigurasi, lihat Menyiapkan metrik sisi klien. Untuk mengetahui daftar metrik yang mendetail, lihat Deskripsi metrik sisi klien.
Metrik sisi klien diukur dari saat permintaan keluar dari aplikasi Anda hingga saat respons diterima oleh aplikasi Anda. Sebaliknya, metrik sisi server diukur dari saat Bigtable menerima permintaan hingga byte data terakhir dikirim ke klien.
Metrik sisi klien tersedia untuk pengguna library klien berikut:
Sebaiknya perbarui semua aplikasi yang terintegrasi dengan
OpenCensus Stats
untuk menggunakan metrik sisi klien Bigtable.
Metrik sisi klien Bigtable ditingkatkan dengan integrasi OpenCensus dan, tidak seperti OpenCensus Stats, Anda tidak dikenai biaya tambahan untuk memublikasikan metrik.
Kapan harus menggunakan metrik sisi klien
Sebaiknya Anda selalu menggunakan metrik sisi klien bersama dengan
metrik sisi server untuk mendapatkan tampilan lengkap dan dapat ditindaklanjuti terkait
performa Bigtable Anda. Melihat metrik dari sisi klien dan server sangat berguna saat Anda mengoptimalkan performa atau memecahkan masalah, dan Anda perlu menentukan di segmen siklus proses permintaan mana masalah terjadi.
Menggunakan kedua jenis metrik sangat berharga untuk jenis workload berikut:
Menayangkan pembacaan jalur di aplikasi komersial dan yang ditampilkan kepada pengguna
Layanan backend penting
Pipeline data skala besar dengan beberapa konsumen
Metrik sisi klien memberi Anda insight tentang bagian siklus proses permintaan yang mungkin menyebabkan latensi:
Perilaku yang diharapkan
Perilaku berikut adalah normal dan sudah diperkirakan:
Waktu mulai satu menit: Setelah Anda mengaktifkan metrik sisi klien, biarkan aplikasi Anda berjalan setidaknya selama satu menit sebelum Anda memeriksa metrik yang dipublikasikan.
Perbedaan kecil antara latensi server dan latensi percobaan klien:
Setelah mengaktifkan metrik sisi klien, Anda mungkin melihat perbedaan satu digit antara metrik bigtable.googleapis.com/server/latencies dan bigtable.googleapis.com/client/attempt_latencies yang sebelumnya tidak Anda ketahui. Misalnya, jika aplikasi Anda menggunakan VM Compute Engine dan Bigtable di region yang sama, perbedaan antara latensi percobaan klien dan latensi server menunjukkan latensi jaringan. Untuk 350 kueri per detik (QPS) dan ukuran payload 5 KB, latensi jaringan sekitar 4 md. Latensi ini sudah diperkirakan.
Biaya
Tidak ada biaya untuk melihat metrik sisi klien di Cloud Monitoring. Jika Anda menggunakan Cloud Monitoring API, biaya penggunaan mungkin berlaku. Lihat
harga Google Cloud Observability
untuk mengetahui detailnya.
Batasan
Metrik sisi klien tidak didukung untuk aplikasi yang mengintegrasikan
library klien Dataflow atau Apache Beam dengan klien
HBase Bigtable untuk Java.
[[["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\u003eBigtable provides client-side metrics to complement server-side metrics for optimizing performance and troubleshooting issues.\u003c/p\u003e\n"],["\u003cp\u003eClient-side metrics measure the time from when a request leaves the application to when the response is received, differing from server-side metrics.\u003c/p\u003e\n"],["\u003cp\u003eThese metrics are accessible via Cloud Monitoring, its API, and Bigtable monitoring, and are available for Java and Go client libraries.\u003c/p\u003e\n"],["\u003cp\u003eUsing both client-side and server-side metrics together gives a comprehensive view of Bigtable performance, particularly useful for user-facing apps, critical backend services, and large data pipelines.\u003c/p\u003e\n"],["\u003cp\u003eThere are no additional costs to view these metrics in Cloud Monitoring, although Cloud Monitoring API usage may have associated fees.\u003c/p\u003e\n"]]],[],null,["# Client-side metrics overview\n============================\n\nBigtable provides client-side metrics that you can use together\nwith server-side metrics to optimize performance and troubleshoot performance\nissues if they occur.\n\nThis page provides an overview of Bigtable client-side metrics and\ndiscusses when to use them. For setup and configuration instructions, see [Set\nup client-side metrics](/bigtable/docs/client-side-metrics-setup). For a\ndetailed list of the metrics, see [Client-side metrics\ndescriptions](/bigtable/docs/client-side-metrics-descriptions).\n\n*Client-side metrics* are measured from the time a request leaves your\napplication to the time the response is received by your application. In\ncontrast, *server-side metrics* are measured from the time\nBigtable receives a request until the last byte of data is sent to\nthe client.\n\nClient-side metrics are available for users of the following client libraries:\n\n- [Bigtable client library for C++](/cpp/docs/reference/bigtable/latest)\n- [Bigtable client library for Java](/java/docs/reference/google-cloud-bigtable/latest/overview)\n- [Bigtable HBase client for Java](https://github.com/googleapis/java-bigtable-hbase)\n- [Bigtable client library for Go](https://pkg.go.dev/cloud.google.com/go/bigtable)\n- [Bigtable client library for Node.js](/nodejs/docs/reference/bigtable/latest)\n\nYou can access client-side metrics in one of the following ways:\n\n- [Cloud Monitoring](/monitoring/docs/monitoring-overview), under **Metrics Explorer**\n\n- [Cloud Monitoring API](/monitoring/api/v3)\n\n- [Bigtable system insights](/bigtable/docs/monitoring-instance)\n\nWhen to upgrade\n---------------\n\nWe recommend that you update all applications integrated with\n[OpenCensus Stats](https://www.google.com/url?sa=D&q=https%3A%2F%2Fgithub.com%2Fgoogleapis%2Fjava-bigtable%2Ftree%2Fv2.15.0%23enabling-cloud-bigtable-metrics-opencensus-stats)\nto use Bigtable client-side metrics instead.\nBigtable client-side metrics improve on the OpenCensus integration\nand, unlike with OpenCensus Stats, you incur no additional cost for publishing\nthe metrics.\n\nWhen to use client-side metrics\n-------------------------------\n\nWe recommend that you always use client-side metrics in conjunction with\nserver-side metrics to get a complete, actionable view of your\nBigtable performance. Viewing metrics from both the client and\nserver sides is especially useful when you are optimizing performance or\ntroubleshooting issues, and you need to determine in which segment of the\nrequest lifecycle a problem is occurring.\n\nUsing both types of metrics is especially valuable for the following types of\nworkloads:\n\n- Serving path reads in user-facing and commercial applications\n- Critical backend services\n- Large-scale data pipelines with multiple consumers\n\nClient-side metrics give you insight into which portion of the request lifecycle\nmight be causing latency:\n\nExpected behaviors\n------------------\n\nThe following behaviors are normal and expected:\n\n- **One-minute startup time**: After you enable client-side metrics, let\n your application run for at least a minute before you check for any\n published metrics.\n\n- **Minor differences between server latencies and client attempt latencies** :\n After enabling client-side metrics, you might notice a single-digit\n difference between the `bigtable.googleapis.com/server/latencies` and\n `bigtable.googleapis.com/client/attempt_latencies` metrics that you were\n previously not aware of. For example, if your application uses a\n Compute Engine VM and Bigtable in the same region, the\n difference between client attempt latencies and server latencies shows the network\n latencies. For 350 queries per second (QPS) and payload size 5 KB, the network latency is around 4 ms.\n This latency is expected.\n\nCosts\n-----\n\nThere is no charge to view client-side metrics in Cloud Monitoring. If you\nuse the Cloud Monitoring API, usage fees might apply. See\n[Google Cloud Observability pricing](/stackdriver/pricing)\nfor details.\n\nLimitations\n-----------\n\nClient-side metrics are not supported for applications that integrate\nDataflow or Apache Beam client libraries with the Bigtable\nHBase client for Java.\n\nWhat's next\n-----------\n\n- [Install and configure client-side metrics.](/bigtable/docs/client-side-metrics-setup)\n- [View the complete list of client-side metrics.](/bigtable/docs/client-side-metrics-descriptions)"]]
