Cloud Service Mesh dan Traffic Director kini bergabung menjadi Cloud Service Mesh. Untuk mengetahui informasi selengkapnya, lihat ringkasan Cloud Service Mesh.
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Ringkasan kemampuan observasi
Cloud Service Mesh memberikan kemampuan observasi terkait kondisi dan performa layanan Anda. Untuk mendapatkan data telemetri, Cloud Service Mesh mengandalkan
proxy file bantuan
yang Anda masukkan sebagai penampung terpisah ke dalam Pod yang sama dengan workload Anda.
Proxy mencegat semua traffic HTTP masuk dan keluar ke workload serta
melaporkan data ke Cloud Service Mesh. Dengan sistem ini, developer layanan
tidak perlu melengkapi kode mereka untuk mengumpulkan data telemetri.
Cloud Monitoring dan Cloud Logging diaktifkan di projectGoogle Cloud saat Anda menginstal Cloud Service Mesh. Untuk melaporkan data telemetri, setiap proxy file bantuan yang dimasukkan ke dalam Pod layanan Anda akan memanggil Cloud Monitoring API dan Cloud Logging API. Data telemetri akan otomatis diupload ke halaman Cloud Service Mesh di konsolGoogle Cloud . Perhatikan bahwa metrik hanya ditampilkan untuk layanan HTTP di halaman Cloud Service Mesh di konsol Google Cloud .
Cloud Service Mesh menyediakan beberapa dasbor layanan yang telah dikonfigurasi sebelumnya di
konsolGoogle Cloud sehingga Anda tidak perlu menyiapkan dasbor dan
diagram secara manual. Telemetri mendetail ini memungkinkan operator mengamati perilaku layanan,
dan memungkinkan mereka memecahkan masalah, memelihara, dan mengoptimalkan aplikasi mereka.
Di halaman Cloud Service Mesh di Google Cloud konsol, Anda dapat:
Dapatkan ringkasan semua layanan di mesh Anda, yang memberikan metrik tingkat layanan kritis pada tiga dari empat sinyal emas pemantauan: latensi, traffic, dan error.
Tentukan, tinjau, dan tetapkan pemberitahuan berdasarkan tujuan tingkat layanan (SLO),
yang merangkum performa layanan yang terlihat oleh pengguna.
Lihat diagram metrik untuk setiap layanan dan analisis secara mendalam dengan pemfilteran dan pengelompokan, termasuk menurut kode respons, protokol, pod tujuan, sumber traffic, dan lainnya.
Dapatkan informasi mendetail tentang endpoint untuk setiap layanan, dan lihat
cara traffic mengalir di antara layanan, serta seperti apa performanya
untuk setiap edge komunikasi.
Jelajahi visualisasi grafik topologi layanan yang menunjukkan layanan
mesh dan hubungannya.
[[["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."],[],[],null,["# Observability overview\n======================\n\nCloud Service Mesh provides *observability* into the health and performance\nof your services. To obtain telemetry data, Cloud Service Mesh relies on\n[sidecar proxies](/service-mesh/docs/onboarding/kubernetes-workloads#inject_sidecar_proxies)\nthat you inject as a separate container into the same Pods as your workloads.\nThe proxies intercept all inbound and outbound HTTP traffic to the workloads and\nreport the data to Cloud Service Mesh. With this system, service developers\ndon't have to instrument their code to collect telemetry data.\n\nCloud Monitoring and Cloud Logging are enabled in your\nGoogle Cloud project when you install Cloud Service Mesh. To report\ntelemetry data, each sidecar proxy that is injected into your service Pods calls\nthe Cloud Monitoring API and the Cloud Logging API. The telemetry data is\nautomatically uploaded to the Cloud Service Mesh pages in the\nGoogle Cloud console. Note that metrics are displayed only for HTTP services\non the Cloud Service Mesh pages in the Google Cloud console.\n\nCloud Service Mesh provides several preconfigured service dashboards in the\nGoogle Cloud console so you don't have to manually set up dashboards and\ncharts. This detailed telemetry enables operators to observe service behavior,\nand empowers them to troubleshoot, maintain, and optimize their applications.\n\nOn the Cloud Service Mesh pages in the Google Cloud console, you can:\n\n- Get an overview of all services in your mesh, providing you critical,\n service-level metrics on three of the\n [four golden signals of monitoring](https://sre.google/sre-book/monitoring-distributed-systems/#xref_monitoring_golden-signals):\n latency, traffic, and errors.\n\n- Define, review, and set alerts against service level objectives (SLOs),\n which summarize your service's user-visible performance.\n\n- View metric charts for individual services and deeply analyze them with\n filtering and breakdowns, including by response code, protocol, destination\n pod, traffic source, and more.\n\n- Get detailed information about the endpoints for each service, and see\n how traffic is flowing between services, and what performance looks like\n for each communication edge.\n\n- Explore a service topology graph visualization that shows your mesh's\n services and their relationships.\n\nWhat's next\n-----------\n\n- [Control access to Cloud Service Mesh in the Google Cloud console](/service-mesh/docs/access-dashboard)\n- [Learn about SLOs](/service-mesh/docs/observability/slo-overview)\n- [Create an alerting policy on an SLO](/service-mesh/docs/observability/alert-policy-slo)"]]
