Cloud Service Mesh 可讓您觀測服務的健康狀態和效能。為了取得遙測資料，Cloud Service Mesh 會使用附屬代理伺服器，您可以將其做為獨立容器，插入與工作負載相同的 Pod 中。這些 Proxy 會攔截所有傳入和傳出的工作負載 HTTP 流量，並將資料回報至 Cloud Service Mesh。有了這個系統，服務開發人員就不必收集遙測資料來檢測程式碼。
安裝 Cloud Service Mesh 時，系統會在Google Cloud 專案中啟用 Cloud Monitoring 和 Cloud Logging。為了回報遙測資料，每個插入服務 pod 的補充 Proxy 都會呼叫 Cloud Monitoring API 和 Cloud Logging API。遙測資料會自動上傳至 Google Cloud 控制台的 Cloud Service Mesh 頁面。請注意，只有 HTTP 服務的指標會顯示在Google Cloud 主控台的 Cloud Service Mesh 頁面中。
Cloud Service Mesh 在Google Cloud 控制台中提供多個預先設定的服務資訊主頁，因此您不必手動設定資訊主頁和圖表。這項詳細的遙測資料可讓營運人員觀察服務行為，並協助他們排除應用程式問題、維護應用程式並進行最佳化。
在 Google Cloud 控制台的 Cloud Service Mesh 頁面中，您可以執行下列操作：
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-04 (世界標準時間)。"],[],[],null,["# Observability overview\n======================\n\nCloud Service Mesh provides *observability* into the health and performance of\nyour services. To obtain telemetry data, Cloud Service Mesh relies on\n[sidecar proxies](/service-mesh/v1.20/docs/anthos-service-mesh-proxy-injection) that you inject as a\nseparate container into the same pods as your workloads. The proxies intercept\nall inbound and outbound HTTP traffic to the workloads and report the data to\nCloud Service Mesh. With this system, service developers don't have to instrument\ntheir 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 telemetry data,\neach sidecar proxy that is injected into your service pods calls the\nCloud Monitoring API and the Cloud Logging API. The telemetry data is automatically\nuploaded to the Cloud Service Mesh pages in the Google Cloud console. Note that\nmetrics are displayed only for HTTP services on the Cloud Service Mesh pages in the\nGoogle 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/v1.20/docs/access-dashboard)\n- [Learn about SLOs](/service-mesh/v1.20/docs/observability/slo-overview)\n- [Create an alerting policy on an SLO](/service-mesh/v1.20/docs/observability/alert-policy-slo)"]]
